New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
copy_local: false
has no effect when opening .NET SDK projects with VS2017
#3352
Comments
copy_local: false
has no effect with .NET SDK when using VS2017copy_local: false
has no effect when using .NET SDK projects with VS2017
Even if I first do |
If I add the <PackageReference Include="Argu">
<Version>5.1</Version>
<ExcludeAssets>runtime</ExcludeAssets>
</PackageReference> |
copy_local: false
has no effect when using .NET SDK projects with VS2017copy_local: false
has no effect when opening .NET SDK projects with VS2017
Kind of related: #3186 |
Description
When using the new .NET SDK project format, setting
copy_local: false
for a package does not work as expectedwhen opening the project in VS2017
.Repro steps
In a new empty directory, create a new F# project
Edit the project file and replace netstandard2.0 with net462
<TargetFramework>net462</TargetFramework>
Invoke
paket init
Edit paket.dependencies (note copy_local: false)
Edit paket.references
Argu
Invoke
paket install
Now open the project in VS2017 and build from there.
The problem is that VS2017 generates the
project.assets.json
when opening the project and that seems to ignore theExcludeAssets
tag.Expected behavior
Argu.dll
not to appear in thebin
folderActual behavior
Argu.dll
does appear in thebin
folderKnown workarounds
Delete the
obj
folder and don't open the solution in VS and build withdotnet build
instead.However, if you open the solution in VS2017 afterwards, the
project.assets.json
is changed and things are broken again (it fills in theruntime
asset).The text was updated successfully, but these errors were encountered: