-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need help resolving prerelease NuGet packages #976
Comments
This is a common error. And I will change the semantics soon so that people To solve your issue use only prerelease without any version filter. Or use
|
Thank you very much for the quick reply! I'm slapping my forehead for not realizing sooner what was going on. 😊 |
no as I said it was a common misunderstanding and it is now fixed so that people get what they expect. |
I am having a very difficult time getting NuGet prerelease packages to resolve properly and would really appreciate some help. 😄
What I would like to do is install the latest available of a package, including prereleases. In the example below, I expected Paket to find Microsoft.AspNet.Mvc 6.0.0-beta6. In the future when v7.0 is released, then I would expect that to be resolved.
When I use a pessimistic version range with beta explicitly set e.g.
~> 6.0.0-beta
it is able to resolve. Am I using the right syntax? Based on the examples, I had thought the former would work.Thanks!
The text was updated successfully, but these errors were encountered: