Posted on 04/04/2022 09:13:56
Hi Jesper
Sorry about the inconvenience.
Sometimes we unlist packages - we do that if they contain things that you do not want in production - security issues or (regressional) bugs that are causing bad problems for you. Unlisting is a nuget package is a feature that can be used in these cases - read more here: https://docs.microsoft.com/en-us/nuget/nuget-org/policies/deleting-packages
We understand that it can cause some upgrade problems - but it is to avoid worse problems in your production.
If you have explicit references to a specific version of a package, restore should work on them even though they are unlisted. Your Nuget client (part of your visual studio) has also changed behavior over time related to this, so exactly how it behaves depends on your local nuget version and if your are using packages.config or package references (new format). Ensure to install the latest nuget client.
You can try this - which will re-download and re-install packages:
Update-Package -reinstall
We do whatever we can to avoid unlisting - we know it is annoying and causes frustrations.
Also new projects using package references (instead of packages.config) should automatically fix reference issues. See this one: https://docs.microsoft.com/en-us/nuget/consume-packages/reinstalling-and-updating-packages
Also you can find information on troubleshooting restore of nuget packages here: https://docs.microsoft.com/en-us/nuget/consume-packages/package-restore-troubleshooting
If you have issues getting your packages to update, we can schedule a teams session to help you sort the issue out. Let me know!
BR Nicolai
