Microsoft's Enterprise Library

I recently received a questions regarding the best practices for doing data access.  My company has our own internal data access architecture and code generator that works great.  However, if you are starting a new project and don’t have an established architecture, I would take a serious look at Microsoft’s Enterprise Library as a starting point.  It contains many best practices regarding data access, logging, exception handling and more.  What’s better is you get the source code so you can tweak it as needed.  

There is also some great and affordable training on Enterprise Library available from Innerworkings.  I’ve blogged about Innerworkings before (here).  They have mastered e-learning.  Just go to the catalog on their site and you can find the Enterprise Library training in either VB.Net or C#.  I think the two part series will run you about $60.  Not a bad way to get a quick start in this stuff.

Posted in |

3 comments:

  1. Brian Finnerty Says:

    Ben,

    Thanks for your kind words about InnerWorkings and our Enterprise Library training for .NET developers. We are known to the Enterprise Library team at Microsoft and they have listed InnerWorkings as one of their recommended training providers on Patterns & Practices (alongside Plural Sight and others):

    http://msdn2.microsoft.com/en-us/practices/bb190374.aspx

    Cheers,

    Brian Finnerty
    InnerWorkings

  2. wesnur Says:

    Hi Ben,

    I agree with you that Enterprise Library is a good tool for developers. I worked with caching application block a while back and found it a Godsend for my application’s performance. However, I ran into some issues when I needed to scale my web farm. CAB started giving me integrity problems. I had to use a commercial solution for extending Enterprise Library Caching Application Block to solve that problem. Still, for initial purposes, Enterprise Library is one of the most time saving tools for developers.


    Cheers.

  3. wesnur Says:

    Hi Ben,


    I agree with you that Enterprise Library is a good tool for developers. I worked with caching application block a while back and found it a Godsend for my application’s performance. However, I ran into some issues when I needed to scale my web farm. CAB started giving me integrity problems. I had to use a commercial solution for extending Enterprise Library Caching Application Block to solve that problem. Still, for initial purposes, Enterprise Library is one of the most time saving tools for developers.



    Cheers.