B
Bern McCarty
I know how with VC8 you embed your linker generated manifest into an exe
with a resource ID of #1 and into a dll with resource ID #2. But what do
you do with the linker generated manifest for a mixed .netmodule? Do you
need to embed the it into the .netmodule? If so, with what ID? Or do you
merge the .netmodule linker generated manifest into the manifest that you
embed into the "assembly manifest containing" file?
I have a 2-file assembly. The primary file (the dll that contains the assembly
manifest) is written in C#. The .netmodule is mixed-mode, written in MEC++.
This all worked fine in my multi-domain applications until I recompiled
this multifile assembly with C# 2/VC 8. Now I find that a non-default app
domain cannot access the mixed .netmodule unless it is accessed first in
the default domain. I have a little console app that demonstrates this.
Here is the error:
Unhandled Exception: System.Runtime.Serialization.SerializationException:
Type is not resolved for
member '<CrtImplementationDetails>.ModuleLoadException,msvcm80, Version=8.0.50727.163,
Culture=ne
utral, PublicKeyToken=b03f5f7f11d50a3a'.
at Bentley.Repro.HostApp.UseMultiFileAssembly(String[] args)
at Bentley.Repro.HostApp.Main(String[] args) in c:\temp\MultiFileAssemblyRepro\MultiDomainHostA
pp\MultiDomainHostApp.cs:line 178
This all worked before VC 8.
Bern McCarty
Bentley Systems
with a resource ID of #1 and into a dll with resource ID #2. But what do
you do with the linker generated manifest for a mixed .netmodule? Do you
need to embed the it into the .netmodule? If so, with what ID? Or do you
merge the .netmodule linker generated manifest into the manifest that you
embed into the "assembly manifest containing" file?
I have a 2-file assembly. The primary file (the dll that contains the assembly
manifest) is written in C#. The .netmodule is mixed-mode, written in MEC++.
This all worked fine in my multi-domain applications until I recompiled
this multifile assembly with C# 2/VC 8. Now I find that a non-default app
domain cannot access the mixed .netmodule unless it is accessed first in
the default domain. I have a little console app that demonstrates this.
Here is the error:
Unhandled Exception: System.Runtime.Serialization.SerializationException:
Type is not resolved for
member '<CrtImplementationDetails>.ModuleLoadException,msvcm80, Version=8.0.50727.163,
Culture=ne
utral, PublicKeyToken=b03f5f7f11d50a3a'.
at Bentley.Repro.HostApp.UseMultiFileAssembly(String[] args)
at Bentley.Repro.HostApp.Main(String[] args) in c:\temp\MultiFileAssemblyRepro\MultiDomainHostA
pp\MultiDomainHostApp.cs:line 178
This all worked before VC 8.
Bern McCarty
Bentley Systems