I just published a blog post titled “NuGet: Broken By Design”:
http://blog.nuget.org/20141010/nuget-is-broken.html
This post explains several aspects of how NuGet was initially designed and discusses the pitfalls the approach faces. Ultimately, the post explains that NuGet can’t really provide some expected package management features because it’s limited to what Visual Studio and MSBuild can do. Next, I’ll be working on a post that describes how we plan to tackle these problems with new packaging features, integration with VS and MSBuild, and how we think the transition will play out.
We’d appreciate your thoughts on all of this.
Thanks,
Jeff
As a follow-up to the “Broken By Design” blog post, I published “NuGet: In The Platform” tonight.
http://blog.nuget.org/20141014/in-the-platform.html
This post lays out our plans for how NuGet can become part of the Microsoft development platform, with Visual Studio and MSBuild recognizing NuGet as a first-class concept in projects.
This won’t affect NuGet’s position as an external open-source project, but it does enable us to introduce new package management features over time, where we previously could not.
Thanks in advance for your feedback and input,
Jeff Handley
--
You received this message because you are subscribed to the Google Groups "NuGet Ecosystem" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
nuget-ecosyst...@googlegroups.com.
To post to this group, send email to
nuget-e...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.