News for hackers. Stuff that matters.
Re:A Proposal for Package Versioning in Go by GiorgioG on Monday March 26, 2018 @04:00PM (#16681986)
NuGet / VS has no qualms with having two references to the same package, but different versions in the project file (i.e. Newtonson.Json.dll 9.0 and 10.0) The build will likely fail though and you'll get no visual feedback that there are two refs in the VS NuGet UI. How did we we get in that state to begin with? I suspect through bad project file merges (or possibly NuGet UI bugs, can't say for sure.)
Re:A Proposal for Package Versioning in Go by flukus on Monday March 26, 2018 @08:53PM (#16684192)
> How did we we get in that state to begin with? I suspect through bad project file merges (or possibly NuGet UI bugs, can't say for sure.)

Most likely someone modified the packages for an individual project and not the solution as a whole. Always manage packages at the solution level and your much less likely to have these issues, unless you have multiple solutions...

Re:A Proposal for Package Versioning in Go by GiorgioG on Monday March 26, 2018 @10:59PM (#16684826)
That sounds great when you have a small team, with 30+ devs it's hard to police.