Closed rheone closed 4 years ago
This issue should be resolved in the next release of Visual Studio 16.5. see https://github.com/NuGet/Home/issues/8772#issuecomment-548958530
We are doing this work. Done now, but need some improvements. So likely shipping in VS 16.5. #8189 is tracking that work.
Until then, packages can choose to use the new technique, and leave the old url in the project and/or nuspec -- that will stop the warning, and still work in versions of VS that don't know how to show it yet.
Should we do anything for backwards compatibility?
After discovering stackoverflow "NuGet Package Icon Not getting Displayed" it appears that the PackageIcon csproj directive is not respected by the Nuget PackageManager within Visual Studio a documented issue that appears to be getting attention.
icon
andiconUrl
are deprecated, but supported by both NuGet site and Nuget PackageManager within Visual StudiopackageIcon
is not supported by Nuget PackageManager within Visual Studio, but is supported by the NuGet site.I would have to assume embedding and
iconUrl
will conflict, but experimentation is required.