Using VS2005 on a project that earlier used VS2003

  • Thread starter Thread starter TonyJ
  • Start date Start date
T

TonyJ

Hello!

What is the right way to go when I have a C++ project that earlier used
VS2003.

When I compile now I get a lot of compile error.

//Tony
 
Hi Tony,

TonyJ said:
Hello!

What is the right way to go when I have a C++ project that earlier used
VS2003.

When I compile now I get a lot of compile error.

Managed or unmanaged C++?

For managed: learn the new syntax for C++/CLI and change the code.

For unmanaged: what are the errors? Typically you will get a lot of warnings
about unsafe APIs which you should replace with safer versions.
 
Hello!

What is the right way to go when I have a C++ project that earlier used
VS2003.

When I compile now I get a lot of compile error.

//Tony

Are you getting errors or warnings? Or both..
Please send a sample of the errors and warning you get.

You should be able to migrate from 2003 C++ projects to 2005 C++
projects fairly easily, but it depends on how compliant your C++ code
was.
Do you have any managed code in the C++ project?

Are you using many of the older C style functions? (such as ones found
in stdio.h). Using these will often give you warnings. Sometime you
can simply disable these warnings for the time being.

Josh
 
Hello!

It's manage code.
Is the best or maybe the only way to take each compile error and correct it.
I just wonder if there exist some way to let the vc2005 behave like vs2003
and compile without error.

//Tony
 
Hello!

It's manage code.
Is the best or maybe the only way to take each compile error and correct
it.
I just wonder if there exist some way to let the vc2005 behave like
vs2003
and compile without error.

/clr:oldSyntax might help (although I never tried it as I upgraded from
Managed C++ to CLI/C++).

Boris
 
Back
Top