You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know how Nuget works under the covers -- but the NGDD does not fetch some older deps that are supposedly satisfied by later versions (e.g. Microsoft.AspNetCore 1.1.x is not downloaded because another dep from another targeted framework already fetched Microsoft.AspNetCore 2.0.x).
This is a problem when the packages are brought over to an offline system and installed with NuGet Package Manager which sometimes demands the older 1.1.x packages. I don't know why the NPM is not satisified with 2.0.x when supposedly >= 1.1.x is required.
To "fix" the "problem" I modified GetRangedPackageVersion:
See my post at https://stackoverflow.com/questions/57116073/nuget-exe-and-nuget-package-manager-resolve-different-dependencies/57150898#57150898
I don't know how Nuget works under the covers -- but the NGDD does not fetch some older deps that are supposedly satisfied by later versions (e.g. Microsoft.AspNetCore 1.1.x is not downloaded because another dep from another targeted framework already fetched Microsoft.AspNetCore 2.0.x).
This is a problem when the packages are brought over to an offline system and installed with
NuGet Package Manager
which sometimes demands the older 1.1.x packages. I don't know why the NPM is not satisified with 2.0.x when supposedly >= 1.1.x is required.To "fix" the "problem" I modified
GetRangedPackageVersion
:The text was updated successfully, but these errors were encountered: