Attention: We have retired the ASP.NET Community Blogs. Learn more >

Hands-on Labs for Microsoft Enterprise Library 4.1 and Unity 1.2

In case you didn't notice yet, there are new HOLs for EntLib 4.1 and Unity 1.2.

Included in this release are three new hands-on labs covering:-          Interception (with Policy Injection Application Block and Unity)-          Dependency Injection with Unity-          Validation Application BlockThere are also updates of the hands-on labs for the following blocks:−        Caching Application Block

−        Cryptography Application Block

−        Data Access Application Block

−        Exception Handling Application Block −        Logging Application Block −        Security Application BlockClick here to download the complete set of Hands-on Labs for Enterprise Library 4.1.
Unity 1.2 Hands-on Labs are also available as a separate download.

Additionally, a comprehensive set of Frequently Asked Questions is now available online.

Further details can be found in Grigori's blog. 

5 Comments

  • CAB (Cashing Application Block) in the Enterprise Library is been implanted to simplify development tasks but due to it’s in process and standalone behavior it reduces the performance of the application which is not in most case tolerate able. This drawback can be overcome by using third party integrations including NCache which is free available and can be tested for the performance and scalability

  • CAB (Cashing Application Block) in the Enterprise Library is been implanted to simplify development tasks but due to it’s in process and standalone behavior it reduces the performance of the application which is not in most case tolerate able. This drawback can be overcome by using third party integrations including NCache which is free available and can be tested for the performance and scalability

  • CAB (Cashing Application Block) in the Enterprise Library is been implanted to simplify development tasks but due to it’s in process and standalone behavior it reduces the performance of the application which is not in most case tolerate able. This drawback can be overcome by using third party integrations including NCache which is free available and can be tested for the performance and scalability

  • Enterprise Library 4.1 Hands-on-Lab 7 Task 4 is concerned with using a ValidationProvider added to the VS2008 Designer and configuring it with an ErrorProvider. The ValidationProvider is then applied to both the Customer and Address fields in MainForm. When the test application is run, if you leave all the fields blank and click the Accept button, an errorprovider icon is shown on the First Name field with an appropriate message when you mouse over it. However, there appear to be some problem areas. Here are my questions.
    1. Why are there no errorprovider icons on the other invalid fields?
    2. If I correct the First Name by entering a valid first name, and click Accept, instead of getting an errorprovider icon on the next invalid field, I get the MessageBox popup showing all the invalid fields (without First Name, which is now valid).
    3. If I quit the application, restart it, enter a valid name for First Name, and click Accept, I expect to get an errorprovider icon on at least the new first invalid field, Last Name, but instead I get the MessageBox popup.
    The implementation of ValidationProvider with ErrorProvider does not seem to operate as one would expect. What is needed to show the ErrorProvider icons on all invalid fields?
    Thanks,
    nick.piazza@carefusion.com

  • Hi Nick,
    You may try posting your questions to the EntLib thread here: http://entlib.codeplex.com/Thread/List.aspx

    Thanks,
    Hernan

Comments have been disabled for this content.