Which framework to use in my enterprise application?

.NET Framework: Does anyone use Enterprise Library these days?

  • Few years ago, every .NET developer I worked with would use Enterprise Library for a lot of common things. Even back then I always found the syntax of Enterprise Library to be bit out of date. They recently released version 6 of it that caught my eyes. Are there people in industry, other than Microsoft consultants, who are using this tool? http://entlib.codeplex.com/

  • Answer:

    I'm a consultant in the Midwest and have been using Enterprise Library heavily since 1.0. It's true that some of the blocks in the library are less necessary as the technology space evolves, Caching is a good example of something the .NET core improved on and the block has been removed. However, blocks are always being improved or new ones are being added. Personally I would recommend looking at the Transient Fault Block and the Semantic Logging Block. Both are areas that the .NET core is still evolving and they provide a lot of value to applications that need to be resilient and distributed.

Daniel Piessens at Quora Visit the source

Was this solution helpful to you?

Other answers

I haven't been keeping up with more recent versions of Enterprise Library, but I recall using it in a project several years ago. My take away was that it wasn't for me. Enterprise Library doesn't seem like a "celebrated" topic in the .net community either, but I couldn't give you any data on its current usage in new projects.

Torgeir Helgevold

Unfortunatly, yes. In my opinion, EF is one of those frameworks created both to "simplify" development, and to remove the requirement for the developer to understand SQL. This might work well for very small projects. Projects that are developed once, and then are not expected to grow, or have a short lifespan. However, to develop a data-driven appliaction without an understanding of databases is in my opinion madness. Further, when schemas start changing, models are added, etc., then using EF actually starts beeing a much greater bother than just doing it right from the start. Also, the "coding by convention" approach seems to be very much in vouge theese days, but it has one _major_ limitation: There's no way a developer not familiar with the framework can intuitively understand exactly what it does. This would make the project very difficult to maintain at some later time when the given framework utlilizing convetion is no longer popular.

Christian Ruud

Just Added Q & A:

Find solution

For every problem there is a solution! Proved by Solucija.

  • Got an issue and looking for advice?

  • Ask Solucija to search every corner of the Web for help.

  • Get workable solutions and helpful tips in a moment.

Just ask Solucija about an issue you face and immediately get a list of ready solutions, answers and tips from other Internet users. We always provide the most suitable and complete answer to your question at the top, along with a few good alternatives below.