index > Visual Studio Team System - Architects > Application locked - error creating configuration section handler

Application locked - error creating configuration section handler

I am using the patterns and practices Enterprise Library for .NET Framework 2.0, so the web.config files of my middle tier web services of my app contains configuration for the enterprise library exception handling and logging. For example:

<?xml version="1.0"?>
<configuration>
<configSections>
<section name="exceptionHandling" type="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Configuration.ExceptionHandlingSettings, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling"/>
<section name="loggingConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.LoggingSettings, Microsoft.Practices.EnterpriseLibrary.Logging"/>
</configSections>
<connectionStrings>
...

The AD diagram cannot load because 'An error occured creating the configuration section handler for loggingConfiguration: Could not load file or assembly ' Microsoft.Practices.EnterpriseLibrary.Logging' or one of its dependencies.'

My app builds and runs fine. The web services in question have references to the enterprise library dlls - so why can't the AD designer find them?

These web services were originally designed on the AD diagram, and implemented from there. This has broken since I configured the enterprise libary exception handling and logging.

Andy Wigley

We are investigating the issue and will respond to this thread as soon as we have more info.

Thanks for your patience,

Ian
Software Development Engineer
Visual Studio Team Edition for Software Architects

Ian Bavey

After further investigation we have determined that the behavior you are seeing is caused by a bug in Visual Studio Team Edition for Software Architects. Please log a bug at http://lab.msdn.microsoft.com/productfeedback/default.aspx and we will make sure it is fixed.

In the meantime we are in the process of trying to determine if there is a workaround that will allow you to unlock your Application Designer. We will post that as soon as it is available.

We apologize for the inconvenience this bug is causing you. If you have any further questions or issues please don't hesitate to post them here for us to investigate.

Thanks,

Ian
Software Development Engineer
Visual Studio Team Edition for Software Architects

Ian Bavey

To workaround this problem you should copy the assemblies for Microsoft.Practices.EnterpriseLibrary.ExceptionHandling and Microsoft.Practices.EnterpriseLibrary.Logging to the Visual Studio 8\Common7\IDE\PrivateAssemblies directory. When you restart Visual Studio you should be able to open the Application Designer without it locking.

Hope this helps,

Ian
Software Development Engineer
Visual Studio Team Edition for Software Architects

Ian Bavey

Thanks, that works around the problem.
I would add - for anyone else encountering this problem - the exception handling configuration for my application wraps exceptions in a custom exception that I have created. It also configures a custom exception handler (similar to the Enterprise Library exception handling and loging quickstart example).

You must also copy to the \PrivateAssemblies folder the assemblies where your custom exceptions are defined, and where your custom exception handler is defined. Once you have done this, your AD diagram wil synchronize.
However, I look forward to a fix, as it's obviously not desirable to have to copy application assemblies (that are still under development) into the \PrvateAssemblies folder all the time!

Andy Wigley

reply 5