Advantages and Disadvantages of Microsoft Enterprise Library 5.0

Question

1.00/5 (1 vote)

See more:

Hi All,

I am new to Microsoft Enterprise Library 5.0 and I have read for same. I made some trail application program with it. But I am not sure about real performance after deployment.

Kindly share your experience (Entire) of Microsoft Enterprise Library 5.0 during development and deployment.

* Specially Data Access
Regards!
Aman

Posted 26-Aug-11 21:29pm

Aman4.net

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ganesan Senthilvel · Answer 1 · 2011-08-26T22:59:00

I didn't have exposure to EL 5.0; but had experience in 4.1 version. In general, the application block concept is really worthful for .NET developers. They made truly reuable common components for the enterprise application development.

My sepcial vote on Unity and Caching Application Block. Unity is powerful in terms of lightweight and extensible dependency injection container. Caching is useful for the better performance by incorporating pluggable cache providers in their applications.