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
Is your feature request related to a problem? Please describe.
I have created a nuget package (Yueyinqiu.Su.D2lTorchSharp), with some some stable releases uploaded. And then I wanted to add Microsoft.DotNet.Interactive reference, which is in preview, so I have to make the new versions to be pre-releases. Then it looks like:
But #r is not installing the newest pre-release version, even if I have unlisted and deprecated the old releases:
Describe the solution you'd like
I suppose that #r should act as if the unlist packages does not exist at all, unless it is installed as a reference of other packages. Or perhaps we could have some options to control this behavior.
By the way, perhaps it should have some warnings when installing a deprecated package.
Describe alternatives you've considered
I'm using *-*". However it means that one day when there is a stable release uploaded, I shall delete them in all my notebooks...
Hmm.. perhaps it won't bother too much. But the most important is that I believe installing a unlisted version should not be the expected behavior, since I can't do that in visual studio (The unlisted packages seems to be non existent, which is what I expect):
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I have created a nuget package (Yueyinqiu.Su.D2lTorchSharp), with some some stable releases uploaded. And then I wanted to add
Microsoft.DotNet.Interactive
reference, which is in preview, so I have to make the new versions to be pre-releases. Then it looks like:But
#r
is not installing the newest pre-release version, even if I have unlisted and deprecated the old releases:Describe the solution you'd like
I suppose that
#r
should act as if the unlist packages does not exist at all, unless it is installed as a reference of other packages. Or perhaps we could have some options to control this behavior.By the way, perhaps it should have some warnings when installing a deprecated package.
Describe alternatives you've considered
I'm using
*-*"
. However it means that one day when there is a stable release uploaded, I shall delete them in all my notebooks...Hmm.. perhaps it won't bother too much. But the most important is that I believe installing a unlisted version should not be the expected behavior, since I can't do that in visual studio (The unlisted packages seems to be non existent, which is what I expect):
The text was updated successfully, but these errors were encountered: