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

Migration to PackageReference #7578

Closed
rafsanulhasan opened this issue Dec 1, 2018 · 1 comment
Closed

Migration to PackageReference #7578

rafsanulhasan opened this issue Dec 1, 2018 · 1 comment
Labels
Resolution:Question This issues appears to be a question, not a product defect Style:PackageReference

Comments

@rafsanulhasan
Copy link

Details about Problem

I'm working on a Xamarin.Forms solution which includes a Xamarin MAC project. In all the projects, I used Xam.Plugins.Settings NuGet package By James from Microsoft. When I tried to convert the project from PC to PR, I found this warning message propping up into a browser:
"Xam.Plugins.Settings v3.1.1

'content' assets will not be available when the package is installed after the migration."

NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe):VS UI

NuGet version (x.x.x.xxx):

dotnet.exe --version (if appropriate):

VS version (if appropriate): 2017

OS version (i.e. win10 v1607 (14393.321)):

Worked before? If so, with which NuGet version:

Detailed repro steps so we can see the same problem

  1. Create a Xamarin.Forms project

  2. Within that solution Add a Xamarin.MAC project.

  3. Install Xam.Plugins.Settings NuGet package into MacOS project

  4. change the project from PC to PR

...

Other suggested things

Verbose Logs

Please include verbose logs (NuGet.exe -verbosity detailed | dotnet.exe --verbosity diag | etc...)

Sample Project

Very helpful if you can zip a project and paste into this issue!

@nkolev92 nkolev92 added the Resolution:Question This issues appears to be a question, not a product defect label Dec 28, 2018
@nkolev92
Copy link
Member

nkolev92 commented Dec 28, 2018

That's a warning message is as expected.

More info
https://blog.nuget.org/20160126/nuget-contentFiles-demystified.html
#6659

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution:Question This issues appears to be a question, not a product defect Style:PackageReference
Projects
None yet
Development

No branches or pull requests

2 participants