The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I'm sick of NuGet micro-managing my references and shafting me in the process. Why are people releasing stable NuGet packages that reference pre-release versions of things?
I've used McvMailer in my current project which has a reference to T4Scaffolding stuff that in turn reference EF6 PRERELEASE ... whereas all our production code references EF5 ...
I know have a broken solution that compiles but wont run ...
A few other devs I've spoken to are equally fed up with NuGet and the mess it can make in the background. I really don't see the benefits, it just wastes time imho and If I want to carry on using MvcMailer it appears that I have to upgrade everything to a pre-release version of EF ...
Am I Massively missing something here or is NuGet just a total pain in the ass?
Ouch. I feel your pain. I don't use NuGet all that often, most of the time I either download the source and compile it or download the binaries. I actually created a NuGet package downloader to assist with that. I will post a link if you want to see it.
If the problem is a package from Scott Hanselmann, may I suggest you contact him: [^]
Or, perhaps, leave a contact on his January 10, 2013 blog article about using NuGet to do some exotic thing with Google Spreadsheets: [^]
He's responded to me, personally, before.
good luck, Bill
“Thus on many occasions man divides himself into two persons, one who tries to fool the other, while a third, who in fact is the same as the other two, is filled with wonder at this confusion. Thinking becomes dramatic, and acts out the most complicated plots within itself, and, spectator, again, and again, becomes: actor.” From a book by the Danish writer, Paul Moller, which was a favorite of Niels Bohr.