Configuring unmanaged application.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I have an unmanaged mfc applicaiton that (through some COM wrappers)
accesses managed components. Managed components reside in GAC. Managed
components where compiled with Framework 1.1. Now, the problem is that after
installing Framework 2.0, the application no longer works correctly. We've
found that the reason is basically since the managed components are invoked
througth COM wrappers, the framework will use the latest (2.0) versions of
the System.XXX assemblies instead of System.XXX that were used when our
managed components were compiled (version 1.1). I know how to configure the
managed assembly to use the desired assembly version or even to force the
framework version. But, how to configure an unmanaged application to load
the correct system assemblies that are compatible with our managed components
that were compiled against 1.1 framework?

I think the way to do it is to provide Application.exe.Mananifest type of
file that contains
<dependent assmebly> declarations. However, I can't figure out the correct
syntax or even which assemblies to specify in this manifest file. There is
very little help on this type of file other then people trying to enable XP
styles on unmanaged MFC applications.

Any help would be greatly apreciated.
Thanks,
Alex
 
alex_indy said:
I think the way to do it is to provide Application.exe.Mananifest
type of file that contains
<dependent assmebly> declarations. However, I can't figure out the
correct syntax or even which assemblies to specify in this manifest
file. There is very little help on this type of file other then
people trying to enable XP styles on unmanaged MFC applications.
Click to expand...

Use the same format as you do for managed applications and the same name
that you would use for a managed application, ie application.exe.config

Richard
 
Back
Top