Skip to content
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

Keep PrivateAssets on switch-to-projects and back #70

Open
jeremyVignelles opened this issue Jun 19, 2020 · 3 comments
Open

Keep PrivateAssets on switch-to-projects and back #70

jeremyVignelles opened this issue Jun 19, 2020 · 3 comments

Comments

@jeremyVignelles
Copy link

I have a package that is referenced like this:

<PackageReference Include="MyPackage" Version="1.0.0-beta01" PrivateAssets="None" />

When I switch-to-projects and switch-to-packages, the PrivateAssets part is dropped.

Would it be possible to save such properties?

@RicoSuter
Copy link
Owner

Makes sense to keep it in this config file so that the restore (switch-to-packages) reverts the csproj as it was before.

@LORDofDOOM
Copy link

Any news about this issue ? I currently also have basicly a similar Problem with

<PackageReference Include="MyPackage" Version="1.0.0" IncludeAssets="compile" />

IMHO every additional XML Attribute should be preserved and restored after switch back to packages

Thank you :-)

@alexander-lysenko-88
Copy link

Hi

I've faced the same issue with <ExcludeAssets>...</ExcludeAssets> sub-node of PackageReference node.
Once I do switch-to-projects and then go back with switch-to-packages the ExcludeAssets node disappears.
As a result I have to add it back manually, that might be time consuming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants