Locking NuGet updates to major .NET version

Avatar
Lumai
Created

Hi there,

Is there a way to lock NuGet package updates to a particular major version of .NET? Where I work we can only update our .NET version to LTS, so every other year we have to be very careful about not using “Upgrade Packages in Solution”

This occured for .NET 7 and now again for .NET 9

Votes

0

Share

3 comments
Avatar
Dmitry Kazantsev
Created

Hello Lumai,

Thank you for contacting Rider support.

If I properly understand the problem and what you need, you might want to consider using the Central Package Management.

Using per-directory/per-solution/per-project .props files allows specifying exact versions of packages to be used.

If that doesn't help or you have any other questions or difficulties, please let me know.

Have a nice day!

0
Avatar
Lumai
Created

Hi Dmitry,

Thanks for the reply! Central package management is great, but it unfortunately  doesn’t solve the issue I’m having. It’s more around ensuring versions of nuget packages don’t appear as an option to upgrade when they rely on other packages that would unintentionally raise the .NET version of packages. 

0
Avatar
Dmitry Kazantsev
Created

Hello Lumai,

To be on the same page, would you mind elaborating on the problem?

  • How exactly the issue occurs. Share a sample scenario;
  • Why doesn't CPM help in this scenario? It allows specifying NuGet packages versions to be used across Solution/Project/Directory.

  • Is the problem by chance in the fact that Rider allows pressing the "Upgrade" button?

  • Would this help by chance? RIDER-114107 NuGet Package Upgrade in Rider Doesn't Respect Version Ranges

Did you consider using a custom NuGet feed? A responsible person might upload proven-to-work nuget packages there, so that developers might use this NuGet feed instead of NuGet.org.

Have a nice day!

0

Please sign in to leave a comment.