All geek questions in one place

What are the problems of migrating from VC8 (VS2005) to VC9 (VS2008)?

I inherited a very large and complex project (actually it is a “solution” consisting of 119 “projects”, most of which are DLLs) that were built and tested under VC8 (VS2005), and I have the task of porting this to VC9 (VS2008).

The migration process that I used was:

  • Copy the VC8.sln file and rename it. to the VC9.sln file.
  • Copy all the VC8 project files and rename them to VC9 project files.
  • Modify all VC9 project files, with / VC 8 / VC9.
  • Edit VC9.sln, s / vc8 / vc9 /
  • Download VC9.sln using VS2008, and let the IDE 'convert' all the project files.
  • Fix compiler and linker errors until I got a good build.

So far, at this last stage, I have encountered the following problems.

1) The change in the method of decorated names is calculated, which leads to truncation of names.

This is more than just a warning ( http://msdn.microsoft.com/en-us/library/074af4b6.aspx ). Libraries created with this warning will not communicate with other modules. Application of the solution in MSDN was non-trivial, but feasible. I examined this problem separately in How to increase the allowed decorated name length in VC9 (MSVC 2008)?

2) A change that does not allow you to assign zero to an iterator. This is consistent with the specification, and it was fairly easy to find and fix these previously made coding errors. Instead of assigning zero to the iterator, use the value of end ().

3) ANSI. .

4) . . /Zm 999 PCH. PCH , , PCH , .

5) dtors. , , , ctor dtor . , VC9, - , . , , .

6) GUID sln vcproj . , , , , .

, , , QA VC8. VC8, , ( VS2005/VC8). , , VC9, , , .

: VC8 VC9. , , " C++". , .

VC8 , crtexe.c. VC9 , , crtdll.c, , . DLL , , , , . , QA .

DLL?

?

+3
5

DLL?

DELAYLOAD? DLL ?

+1

, , . , , , , undefined /dll. ? ( - VS.NET)

- ( ) , , , , . , , -, Voodoo VC9, . .

0

,

  • DLL , main.dll, , , , mainEntry(). .
  • exe, , DLL- ( ).
  • main.exe main.dll LoadLibrary(), GetProcAddress mainEntry().
0

The solution to the problem was simpler than I originally thought. The initialization order problem was caused by the presence of several global type variables derived from std container types (the main design flaw that preceded my position with this company). The solution was to replace all such globals with plain ones. There were about 100 of them.

Once this was done, the initialization (and destruction) order was under the control of the programmer.

0
source

Source: https://habr.com/ru/post/1698978/

More articles:


All Articles