Topic: Why AcDbMgd.dll was loaded into the main AppDomain?

[Andrey Bushman]

I work with AcCui.dll in my external application (i.e. it is not AutoCAD extension). I do it in the separate AppDomain. But I see that AcDbMgd.dll was loaded into my main AppDomain also. I don't understand why does it happen. The detailed example of my "Hello World" is here. I commented code and showed the screen.



Why does it happen and how can I fix it?

[MickD]

I'd be guessing it's because the .net classes are wrappers over the C++ classes and use/inherit the base wrapper class or interfaces from the main dll.

Sorry Andrey but I have to ask, why you are using the AcCui.dll for an external app though if it has nothing to do with AutoCAD??

[Andrey Bushman]

Sorry Andrey but I have to ask, why you are using the AcCui.dll for an external app though if it has nothing to do with AutoCAD??

I have DLL which is intended for configuring any (or almost any) AutoCAD. It edits registry settings and CUI\CUIX content. This DLL is for using by external applications. So, it can be used for creating of AutoCAD administrating utilities. Also it allows to recovery AutoCAD. For example, below is screen of its base set of interfaces. You can see the settings which it can provide and edit. All these interfaces have implementations. Also the solution has the projects with unit tests (NUnit and JustMock).

[MickD]

Cool, thanks for the explanation

[Andrey Bushman]

I forgot to show the enums:

[Andrey Bushman]

Hm... I think the  Hans Passant's answer is right:

I suppose the word "mixed" applies here. AppDomains are a pure managed concept, they only isolate managed objects. Any memory allocated by native code in a mixed-mode assembly is not isolated. It can't be. The isolation boundary for native code is a process.

If I correctly understood of his answer then any mixed assemblies always will be loaded into the main AppDomain also...