+xThe fix is included in the soon to be released v3.7.0. Please contact [email protected] for an update. version 3.7.0 is forcing me up to upgrade an ASP.NET Core 3.1 app to some .NET 5.0 dependencies, yet AspNetCore has a 2.2.x minimum. This wasn't the case with the previous version we're using. ( looks like the minimum was changed in v 3.6.0) <dependency id="Microsoft.AspNetCore.Authentication" version="2.2.0" exclude="Build,Analyzers" /> <dependency id="Microsoft.AspNetCore.Http" version="2.2.2" exclude="Build,Analyzers" /> <dependency id="Microsoft.Extensions.Caching.Memory" version="5.0.0" exclude="Build,Analyzers" /> <dependency id="Microsoft.Extensions.Logging" version="5.0.0" exclude="Build,Analyzers" /> <dependency id="Microsoft.Extensions.Options.ConfigurationExtensions" version="5.0.0" exclude="Build,Analyzers" /> <dependency id="System.Security.Cryptography.Xml" version="5.0.0" exclude="Build,Analyzers" /> I'm now getting a compilation error as I'm explicitly referencing 3.1.x of common dependencies and getting the NU1601 build error. We have other 3rd party libraries that target netCoreApp3.1 and .NET 5.0 separately and enforce 3.x and 5.0 dependencies. I can't see any way around this error.. Please advise.
|