Recently, I've updated a class library project from .NET 3.5 to target the .NET 4.0 framework. This class library is used as a DotNetNuke module, and Castle.Core and Castle.Windsor are used to perform dependency injection of a connection pool management service.
After loading the new build in DotNetNuke on my own dev PC, everything works as expected, but after attempting a practice install on our test environment, we are seeing errors related to finding the 'Microsoft.Windows.Design.Host' assembly, which I've come to understand is not even able to be added to a project as a reference, because it is only used by Visual Studio to support the control designer screens.
I've been able to capture the exception in visual studio, and it looks like the actual issue might be with the dependency injection from Castle.Core and Castle.Windsor (version 2.5.1). The exception I'm getting is,
[ConverterException: Could not convert from 'ASI.Pooling.Injection.iPoolManager' to System.Type.]
That makes me think that it has something to do with the web.config section for Castle, but nothing has changed in that section at all.
My development manager said to check if it was built in debug mode, but I've checked, and all my projects are building in Release mode (AnyCpu), so that shouldn't be an issue.
Would updating a project from 3.5 to 4.0 add something that uses that assembly 'Microsoft.Windows.Design.Host'?
No comments:
Post a Comment