Geeks With Blogs
Chris Breisch   .NET Data Practices
Search this Blog!
Posted on Wednesday, June 1, 2005 9:58 AM Visual Studio , .NET Development | Back to top

Comments on this post: Enterprise Library vs. .NET 2.0

# re: Enterprise Library vs. .NET 2.0
Requesting Gravatar...
Very well said -- and I very much agree.

I want simplicity, which the .NET framework does pretty well at promoting, but the EL fails to pass this test. It tries to be everything to everybody, and in attempting that it fails to be a good solution for those that just want the most basic features. For that matter, I know people that do need a lot of complex features that report it fails them to, because nothing can be all things to all people, but when you make it complex you take away the ability to be easily extendible (not even by those working on it).

For Data Access, ADO.NET just isn't that hard, and there are certainly other solutions to make it easier and better if you want or need that. Logging has Log4Net which is simpler, better, and far more of a standard. Some of the other blocks may be better, but why do I want to pollute my whole project with all of EL to get a few benefits when by doing so I tie myself to a library that just isn't easily extended when I most need it.

I hate to say it, but I find that the main reason people are using EL is because it is from "Microsoft" -- and we all know that too many Microsoft developers fear anything that comes from elsewhere, or worse many of these have never even looked for other solutions or heard of these other great tools.
Left by Paul Wilson on Jun 01, 2005 10:40 AM

# re: Enterprise Library vs. .NET 2.0
Requesting Gravatar...
Simplicity is the ultimate goal. Sometimes, looking at entlib, it seems that the simplicity of use acheived by the config tool and the 'consistency' is overridden by the underlying complexity that you see when you crack it open, and by the bundled package that makes it harder to evaluate as individual pieces. I am not answering to defend entlib, mind you, but to ask you - what could we do to trim down the external or internal features? The open source suggestion for entlib would be an option, but I'd like to say something that I always stress to our customers - we can write the code, we need you - our customers- help in understanding *what code to write*, what works and what doesn't. But we rely on you being up front about these things. In the team we'll be discussing next week what we can do to address this feedback, change things etc.Maybe open feedback weekly calls? Public stack rank of RFCs? so we produce something that *you* would use in more solutions (regardless of whether it comes from the MS 'mothership'). You have a team in MS who is willing to listen often, and respond by shipping often, so pls let us know what you would want to see. We promise to listen and try to understand and apply the learnings in what we do... Drinking our own kool-aid = death...
Left by Edward Jezierski on Aug 12, 2005 7:28 PM

# Enterprise Library 2.0
Requesting Gravatar...

I was looking around tonight to see if many people have been blogging about the new EntLib release...
Left by Kyle Finley on Jan 23, 2006 11:28 PM

# re: Enterprise Library vs. .NET 2.0
Requesting Gravatar...
please get me a new ebook aboat Hands On Labs for C# 2005.
I am computer engineering.
Left by javad ahvaz on Mar 25, 2006 7:02 AM

Your comment:
 (will show your gravatar)

Copyright © Chris J. Breisch | Powered by: