Visual Studio 2005 Isolated references

If a managed DLL uses an active x control via COM interop and the reference to the interop library is marked as Isolated (via properties) then an assembly manifest is generated.


I've found that this assembly manifest is unusable for managed applications that reference the managed class library.  It includes the underlying COM dll as a file element in the manifest but does not include it in a dependency element; perhaps it's implicit.  Instead, I've found that I have to include the underlying COM dll in a dependency element in the application manifest (app.exe.manifest) and leave it out of the managed dll entirely (e.g., no assembly manifest for the managed dll).

No comments:

Post a Comment