Discussion:
upgrading from Visual Studio 2005 to VS 2013
(too old to reply)
Lynn McGuire
2015-01-06 18:31:24 UTC
Permalink
Raw Message
We are thinking about upgrading from Visual Studio 2005 to VS 2013.

Is there a list anywhere of gotchas?

Thanks,
Lynn
David Lowndes
2015-01-06 21:10:51 UTC
Permalink
Raw Message
Post by Lynn McGuire
We are thinking about upgrading from Visual Studio 2005 to VS 2013.
Is there a list anywhere of gotchas?
What aspects of VS2005 do you use?

As you've posted in a VC++ forum, the C++ compiler and standard
library are more standard conforming, so there may be some parts of
your code that require changes, but they're usually minor and are
generally for the good.

You'll probably find the IDE is slower to start.

If you use the Setup/deployment projects - they're gone, though there
is now a project that's resurrected it, albeit that it doesn't support
XP generation OS's.

Dave
Lynn McGuire
2015-01-06 21:51:16 UTC
Permalink
Raw Message
Post by David Lowndes
Post by Lynn McGuire
We are thinking about upgrading from Visual Studio 2005 to VS 2013.
Is there a list anywhere of gotchas?
What aspects of VS2005 do you use?
As you've posted in a VC++ forum, the C++ compiler and standard
library are more standard conforming, so there may be some parts of
your code that require changes, but they're usually minor and are
generally for the good.
You'll probably find the IDE is slower to start.
If you use the Setup/deployment projects - they're gone, though there
is now a project that's resurrected it, albeit that it doesn't support
XP generation OS's.
Dave
Just Visual C++. We have about 400,000 lines of C++ code in our app.

One of the things that we had to upgrade in our website C++ code when GCC was updated was changing the following:
showStuff ("this string");
where showStuff was char * and had to be upgraded to const char *. I suspect that we will see that since a lot of our C++ code was C
originally.
Post by David Lowndes
You'll probably find the IDE is slower to start.
Not good, I was hoping for a speedup.

We have our own deployment tool, we use the old Wise Installation System to create a single setup.exe file.

Thanks,
Lynn
Lynn McGuire
2015-01-08 21:21:24 UTC
Permalink
Raw Message
Post by David Lowndes
Post by Lynn McGuire
We are thinking about upgrading from Visual Studio 2005 to VS 2013.
Is there a list anywhere of gotchas?
What aspects of VS2005 do you use?
As you've posted in a VC++ forum, the C++ compiler and standard
library are more standard conforming, so there may be some parts of
your code that require changes, but they're usually minor and are
generally for the good.
You'll probably find the IDE is slower to start.
If you use the Setup/deployment projects - they're gone, though there
is now a project that's resurrected it, albeit that it doesn't support
XP generation OS's.
Dave
BTW, would you go to VS 2008, 2010, 2012 or 2013?

Thanks,
Lynn McGuire
David Lowndes
2015-01-08 23:37:08 UTC
Permalink
Raw Message
Post by Lynn McGuire
BTW, would you go to VS 2008, 2010, 2012 or 2013?
That depends on what the project requires particularly with .NET
versions if you do any managed code development.

For most of my native C++ projects I still use VS 2008 despite having
access to all the other versions of VS.

I've usually built my projects with all the later compilers just to
check the sources don't have any lurking problems that the newer
compilers may identify.

Dave
Lynn McGuire
2015-01-12 18:19:49 UTC
Permalink
Raw Message
Post by David Lowndes
Post by Lynn McGuire
BTW, would you go to VS 2008, 2010, 2012 or 2013?
That depends on what the project requires particularly with .NET
versions if you do any managed code development.
For most of my native C++ projects I still use VS 2008 despite having
access to all the other versions of VS.
I've usually built my projects with all the later compilers just to
check the sources don't have any lurking problems that the newer
compilers may identify.
Dave
We do not have any managed code in our app. All C, C++ and Fortran 77.

Thanks,
Lynn

Loading...