Installing is okay, I suppose, but enabling by default?! Yikes.
/rafael
On 10/6/2010 8:45 PM, Nasser Dassi wrote:
Bloody. This just in from ScottGu.
NuPack Integration: ASP.NET MVC
3 automatically installs and enables NuPack as part of its
setup. This makes it trivial to take advantage of NuPack to
find and add lots of MVC extensions and libraries to your
projects.
Well, here they go towards unavoidable bloat in production
MVC deployments! This has some positives, but much more
negatives than ASP.NET developers should have to
put up with.
- nasser
On Wed, Oct 6, 2010 at 10:43 AM,
Garrett Serack <[email protected]>
wrote:
For those of you who are
wondering what NuPack is:
The ASP.NET
team started working on a developer-only & .NET
only package manager a few months back, then decided
to collaborate with some of the guys from the NuProj
project.
They have pooled their efforts to bring out NuPack.
In the longer run, I can see us taking a bunch of
their code for Visual Studio integration, and
*potentially* supporting their packages. I'm still
iffy on that...
Regardless, this changes nothing for us.
G
_______________________________________________
Mailing list: https://launchpad.net/~coapp-developers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~coapp-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~coapp-developers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~coapp-developers
More help : https://help.launchpad.net/ListHelp
|
_______________________________________________
Mailing list: https://launchpad.net/~coapp-developers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~coapp-developers
More help : https://help.launchpad.net/ListHelp
