Re: VC++ 6.0 To .NET
It's probably best if you don't refer to .NET for your questions.
This usually refers to the .NET framewrok which doesn't
seem to be anything you are interested in. VC 8.0 is part of
VS 2005.NET and the confusion comes from there. The
next version is VC 9.0 part of VS 2008 and due to be released
soon. It's your decision whether you want to wait for it or not.
Now, each new version of the VC compiler introduces a few
breaking changes so porting to a new version is, alas, always
interesting. Considering you don't know the original codebase
much, I'd advise you just go ahead and port, fixing issues as they
arise. You should certainly check the list of breaking changes
for your chosen compiler and for any previous versions as well
(e.g. VC 7.0, VC 7.1, and VC 8.0 if you decide to use VC 8.0).
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
<elwilj@gmail.com> wrote in message
news:1190047097.294281.50880@19g2000hsx.googlegroups.com...
I'm new to the MS Visual Studio world. I've just inherited a project
that was written entirely in VC++ 6.0. Should I make the move to VC+
+.NET and bybass VC++ 2005? Does the upgrade to .NET involve a great
deal of code rewrites? What resources are out there to help with this
migration? We are on Windows 2000 and XP machines ... must admit I'm
a unix guy thru and thru but this app needs some work. Does anyone
out there have any recommendations?
Thanks
LJ