Reputation: 26028
Has any one used Microsoft's Enterprise Library, if so what parts of it did you use?
I am using building a website (I guess the client app type is not important, it can be a Windows app as well) with all the architectural layer, and I am specifically interested in the exception handling
, logging
and caching
blocks for now. Any one used these, what were the good and bads of your experience with, any alternatives that you rather decided to use? Performance is a thing that I am also interested in.
I am looking for a decent exception handling framework which is how I came across the exception handling block. Anything other out there?
Is it a wise idea to use the data access block with an MVC application seeing that everybody is the repository pattern with an ORM framework?
I am still researching frameworks, so I would like to hear as many opinions.
Upvotes: 0
Views: 1125
Reputation: 2763
For Exception Handling we initially used ELMAH and Log4NET.. but later shifted to Enterprise Library as the client wished to use a more robust and enterprise ready solution. By no means I am saying that ELMAH or Log4NET is not enterprise ready however EntLib does gives you more power. You can read another post here for more details: ELMAH vs Enterprise Library Exception Handling Block
Is it a wise idea to use the data access block with an MVC application seeing that everybody is the repository pattern with an ORM framework? - I would not recommend using DAB if you are using repository pattern with an ORM framework.. Especially with EntityFramework the whole point of having a DAB goes for toss.
For Caching - I would recommend using Caching app block to start with and check if Velocity comes in by the time you plan to deploy...
Upvotes: 2