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
Just capturing this as a separate item to #15 and some of the discussion in #20.
In my experience the current logic resolves dependencies the same as a standard dotnet restore does. However there could be some corner cases where the behaviour is different.
To ensure dependency resolution is correct I think we should be using the standard nuget libraries as published from https://github.com/NuGet/NuGet.Client
The text was updated successfully, but these errors were encountered:
I'm going to close this with a caveat, we should probably support --framework and --runtime parameters. Or alternatively/additionally the --no-restore option to give users more control. But I think new behaviour introduced in #42 should cover most requirements.
Just capturing this as a separate item to #15 and some of the discussion in #20.
In my experience the current logic resolves dependencies the same as a standard
dotnet restore
does. However there could be some corner cases where the behaviour is different.To ensure dependency resolution is correct I think we should be using the standard nuget libraries as published from https://github.com/NuGet/NuGet.Client
The text was updated successfully, but these errors were encountered: