Enterprise Library as default framework
I think include enterprise library as default framework will become handy as this will help for consistency. As my concern, I think most of development works now need dependency injection (unity), Logging tool and config tool. So why not put enterprise library as the first option
Thank you all for voting on this suggestion. The team has heard you and is considering this request, possibly for a future release.
Deonhe – MSFT .NET Framework team
Mike Brooks commented
While I'm an advocate for DI, defaulting to a specific framework is a bad idea (made even worse by defaulting to Enterprise Library). I prefer to have the flexibility to choose my IoC container and I would rather not start each project by removing Enterprise Library.
Very bad suggestion.Disagree。
Enterprise Library is not good enough, some block is bad design such security block is useless.
.Net framework is too slow and too big now. so don't add this Library to it.
Matt Dotson commented
I do agree that .NET should have a dependency injection framework in it. It should also have a standard interface that ninject, autofac and all the other DI frameworks could implment so I can swap out for a different DI framework if I want.
Rich Czyzewski commented
Couldn't disagree more
Richard Collette commented
The problem I see with this is the lack of frequency with which Microsoft releases fixes, combined with the fact that GAC updates would most likely be needed to implement those fixes. If MS were to in-house this, I believe we would lose the ability to implement our own fixes. There have been some real show stoppers that I have been able to correct on my own in the past, without impacting existing projects, without having to deploy components to all machines, etc. If MS could provide a product that was robust, updated frequently enough and could be distributed simply, then the bundling concerns subside.
Christoph Rüegg commented
Disagree as well
Very bad suggestion. Disagree