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
{{ message }}
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
It would be much more reliable if a convention of "dependency": { 'version': 'version-number', type: 'src' }" was introduced that takes away the guessing involved in knowing where the contents you're working with came from. We can leave the current behavior as is, but using this would remove packages as a source of resolution for that dependency.
The text was updated successfully, but these errors were encountered:
I ran into this issue as part of the version pinning.
Microsoft.AspNet.Http.Core
had been renamed, but the rename was not captured in a test project (https://github.com/aspnet/HttpAbstractions/blob/release/test/Microsoft.AspNet.WebUtilities.Tests/project.json#L5). This should have caused the test to fail compilation. However since earlier builds of this package are available on nuget.org, the package continued to be restored and the tests succeeded.It would be much more reliable if a convention of
"dependency": { 'version': 'version-number', type: 'src' }"
was introduced that takes away the guessing involved in knowing where the contents you're working with came from. We can leave the current behavior as is, but using this would remove packages as a source of resolution for that dependency.The text was updated successfully, but these errors were encountered: