Backward compatibility of DLLs built using Visual C++ 2005

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

Guest

We are having a dll backward compatibility issue since we migrated to .NET
2005.
As part of our product, we build a dll which is used by other products.
Everything was fine when we were build it on VC6. We upgraded our compiler to
..NET 2005 for our new version. The new dll fails to load, we get a runtime
error: R6034. We managed to work it around by creating a manifest file for
the loading executable, but this is not an acceptable work around. Is there a
compiler flag that I can use to make it backward compatible?
 
Hi Madhu!
As part of our product, we build a dll which is used by other products.
Everything was fine when we were build it on VC6. We upgraded our compiler to
..NET 2005 for our new version. The new dll fails to load, we get a runtime
error: R6034. We managed to work it around by creating a manifest file for
the loading executable,
Click to expand...

This is by design and has nothing to do with "backword compatiblility"...
but this is not an acceptable work around. Is there a
compiler flag that I can use to make it backward compatible?
Click to expand...

You can statically link to CRT/MFC.

Greetings
Jochen
 
Madhu said:
We are having a dll backward compatibility issue since we migrated to
.NET 2005.
As part of our product, we build a dll which is used by other
products. Everything was fine when we were build it on VC6. We
upgraded our compiler to .NET 2005 for our new version. The new dll
fails to load, we get a runtime error: R6034. We managed to work it
around by creating a manifest file for the loading executable, but
this is not an acceptable work around. Is there a compiler flag that
I can use to make it backward compatible?
Click to expand...

See if this thread helps:

http://groups.google.com/group/microsoft.public.dotnet.languages.vc/msg/e84703d4e19aa831?hl=en

-cd
 
Hi Carl,
I was using the MT tool to embed the manifest file but, I was using "1" as
the resource ID which did not work. Changing it to 2 works!

Thanks a million,
Madhu
 
Back
Top