views:

19

answers:

0

I implemented a VB.NET user control that integrates features of the Microsoft Enterprise Library 5.0. The DLLs of the EntLib are not registered in the GAC - as suggested by MS. When I try to add my user control DLL to the Visual Studio 2008 ToolBox, I receive an error that basically tells me that it wasn't able to load a type from an assembly and states that it didn't find the respective EntLib DLL.

I copied the EntLib DLLs into the folder from which I chose my user control DLL. That still didn't work.

When I register the EntLib DLL's in the GAC, it works. But then my application referencing my user control won't work anymore. When I try putting the EntLib DLL's into the Public Assemblies folder beneath the Visual Studio 9.0/Common7/IDE folder, my user control DLL can be loaded into the ToolBox but again: The application won't work at runtime. This time it even claims it couldn't find the EntLib DLL again, which makes no sense actually.

What is the preferred (and working) way of working with own user controls that reference 3rd party DLLs that are NOT registered in the GAC so that they work both at Design Time (i.e. can be loaded into the ToolBox and dragged onto a WinForm e.g.) AND Run Time?