When I drop my own UserControl (implemented in Assembly A) onto my Form (Assembly B) Assembly A will be loaded two times into the Visual Studio AppDomain.
Further Infos: The UserControl has custom Root Designers, custom designers and editors which are also implemented in Assembly A. Nothing special is done with loading assemblies in Designer Constructors or Control constructors. When dropping the Control, Assembly A and all dependant Assemblies will be created in the "References" folter of the project. Has anybody seen this phenomenom before, is it a known Visual Studio bug? Forces Visual Studio to load this Assembly a second time before a custom control designer is instantiated? Ralf Heitmann You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
