Sort of, yes, but the trouble with that approach is that there is no semantic correlation between such a 'beta' package and the (eventual) actual release, so that to 'switch' to the eventual release would require actually removing the attached beta package(s) and adding the newly-released version. Not only is this invasive, but the NuGet infrastructure is unable to tell you that your attached beta package has finally 'gone release' meaning that the choice "update to latest version" in NuGet won't of course find the release.
What's really needed is... - a flag in the package to indicate release version vs. pre-release - the ability to specify in NuGet whether you want your referenced version to be narrowly-scoped to only take into account release versions or more broadly-scoped to include all pre-release versions as well when NuGet does its version-checking Unless/until this concept of release vs pre-release package becomes a first-class, fully-integrated concept in NuGet (and its related tooling/ecosystem) any one of the possible work-arounds (the one you suggest, the one we've chosen, or a third, fourth , fifth, etc. idea) will represent some set compromises with some pros and other cons :( We've chosen the present approach because it most-easily supports working within the present NuGet infrastructure to auto-update-to-latest when the final release version is available, but there are (of course) a multitude of possible "work-arounds" to handling this. FWIW, this is actually a broader problem than just 'release' vs. 'pre-release' and extends to 'debug' vs. 'release' -built binaries as well (with their accompanying PDBs, etc.). NuGet's present assumption that "all packages are created equal in all cases" is sadly naive and doesn't really represent all the use-cases that are really needed to be supported by a robust package manager. Over time, we have to hope that these shortcomings will be addressed by the NuGet team, making NuGet more useful for both package authors and package consumers. -Steve B. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/9OY-WPiO_sEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
