NuGet: Broken By Design

64 views
Skip to first unread message

Jeff Handley

unread,
Oct 11, 2014, 2:25:52 AM10/11/14
to NuGet Ecosystem (google group)

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

Jeff Handley

unread,
Oct 14, 2014, 10:48:33 PM10/14/14
to NuGet Ecosystem (google group)

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.

Alex Papadimoulis

unread,
Oct 26, 2014, 2:34:15 AM10/26/14
to nuget-e...@googlegroups.com, jeff.h...@microsoft.com
Been out of town and just finally catching up.  My first impression was... wait, whaaaaaa!? That sounds like one of my rants!

I'm glad to see you guys recognize the challenges and have a vision moving forward; I could never tell if you guys just didn't understand these "fundamentally broken" aspects of the platform, or just didn't think they should be fixed. Anyway, good stuff!

It sounds like 3.0 grew a bit in scope? Do you have a rough roadmap for some of this stuff? The last we heard of 3.0 was that CTP blog many months ago, and the target date was something like September I think.

Actually... would you be willing to do a meeting with key partners/vendors to help give us some better insight into the direction of things? A conference call, or whatever, where you could present a roadmap and we can ask questions would be ideal.

What's going to create a very poor experience for our mutual customers is if nuGet 3.0 just all of a sudden is released, and then us vendors have to scramle to reverse engineer how it all works and implement our things.
Reply all
Reply to author
Forward
0 new messages