Supporting multiple versions of NuGet package in one library / NuGet package

Question

What I want

I want my library to work with a range of versions of a NuGet package with breaking changes in API between the changes. I haven\'t investigated it furt

Answer 1

NuGet only resolves single package versions.

If you declare a dependency on the minimum supported version, any referencing project can upgrade the dependency to a newer version.

As long as the authors of the dependent package don't introduce breaking changes, it should work find.

Even if you use reflection to look at the actual assembly versions used, you will find that many package authors don't change the assembly version between releases. This is to avoid the need for binding redirects in classic .NET Framework projects as all versions are the same and NuGet will select the right DLL based on the resolved package version of the consuming project. Again, this is good for as long as there are no breaking changes.

A pattern you could use to support different packages is to provide many "platform" packages that the consumer can choose from. The platform-specific package would then reference a common package with shareable logic.

The "platform" would then be e.g. "MyLogic.XUnit" or "MyLogic.NUnit" (assuming test helpers as example) referencing "MyLogic.Common"