I sometimes get weird things like this most of it is due to versioning problems as the original assembly wants an older version ( it does notupdate until you read add the object to the control) .
If you write a batch file to compile things I doubt you will have any trouble, Speaking of which has anybody tried c++ makefiles with c# and .NET ? I know Visual Studio supports it just want to know if it is worth installing another Gig for C++ stuff. Ben -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Ralf Heitmann Sent: Tuesday, 7 May 2002 3:52 PM To: [EMAIL PROTECTED] Subject: [DOTNET] Visual Studio Bug?, Assembly loaded more than once in AppDomain 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. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
