migration from Visual c++ 2003 to visual c++ 2005

[dipak_mistry]

Hi,

We are in process of migration from Visual c++ 2003 to

visual c++ 2005.(VC 7 to VC 8)

and our binaries are kind of native binary, not managed binaries.

My question is that .....

Will VC 8 binaries work with VC 7 binaries.



Suppose there are 100 dll in my Application which are generated under VC 7.

Now I migrate only 50 of them to VC 8. and let other binary be in VC 7.

Now I make integration(create a setup) and install it on clean/fresh machine.

will my application will work under this mixed environment?

Is it necessary to convert all dll from VC 7 to VC 8?

Please guide me.

Thanks and regards

[cilu]

If the DLLs are independent one on the other, it should be ok. If they have interdependency (which I expect), you'll have problems. For instance they will be linked with different version of runtime library, which is likely to cause problems.

You can use dependency walker (www.dependencywalker.com) to check the dependencies of your executables (DLL, EXE).

[dipak_mistry]

HI,

Thanks you very much for your quick reply!!

Also , suppose my binaries are kind of independent one, then VC ++ 7 binaries will work under framwork 2.0 (as framwork 2.0 required for vc ++ 8 binaries)

regards,

[cilu]

Well, you said your DLLs are native, not managed. So, they don't have anything to do with the .NET framework. Or, did I understand that wrong?

[dipak_mistry]

Ohh , I understand,

Thany again for your help!

[Andreas Masur]

Suppose there are 100 dll in my Application which are generated under VC 7.

Now I migrate only 50 of them to VC 8. and let other binary be in VC 7.

I wouldn't advise such a scenario. Usually, you would try to avoid having mixed-build libraries. Furthermore, why don't you only migrate 50 out of 100. Why not all in the first place?