Hi,

This is a large project. I will try to narrow down the problem down as
simply as I can

- I have an app compiling and running from: "c:\myapp\myapp.exe"

- The app's main form has an Assembly member

- The main form loads up an assembly from "c:\\assembly\\myassembly.dll"
using the following command (names changed): this.myAssembly =
AppDomain.CurrentDomain.Load(AssemblyName.GetAssemblyName(c:\\assembly\\myassembly.dll"));

- Needless to say there is no project reference between my application and
the "myassembly.dll"

- At this point, I can easily instantiate types from the assembly using
"Activator.CreateInstance(type)" - everything works fine.

- The problem: The main from has a property grid. I want it to use custom
type editor and a custom type converted that reside in myassembly.dll - you
do that by passing their assembly qualified name, which I do. The property
grid crashes!

- The solution

Change nothing but have a copy of myassembly.dll reside in the folder where
myapp.exe runs from  (even if the dynamic assembly is being dynamically
loaded from its original path!!!)  - when I do that, the property grid does
not crash on my custom type editor and type converter classes. It's like the
property grid only looks for the assembly in the current executable folder.
weird.

My question is: why do I need to have a copy of the myassembly.dll reside at
the myapp.exe folder for it to work.

Ron