fpdave100 wrote:
or try loading in a separate appdomain, which can be unloaded when it is finished with
But then the type can't be used in the appdomain of the designer: for reflection based purposes that indeed would solve it, but the type object itself is used in the object model in v4.x, so the assembly itself is loaded into the appdomain. I now realize that fixing with shadowcopy won't work: reloading it won't work, as unloading the older version won't work.
The only thing that would solve it is that the designer uses strings as type names, not type objects. We then could load the assembly in another appdomain, inspect the types there, and unload it after marshalling back the type strings to the current appdomain. This is planned in a future update, but not in v4.x