Re: Migrating from Visual C++ 6 to C++.NET

Tech-Archive recommends: Fix windows errors by optimizing your registry

David++ wrote:
> Hi,
>
> I'm trying to compile a project in C++.Net which was built using
> Visual C++
> 6. I'm getting some major compile errors and need to find a solution
> soon. I can either try and convert the project so it is compatible
> with .NET (which I think will be error prone and risky) or I can
> downgrade to Visual C++ 6 and build the project there. The problems
> I'm having are this -
>
> 1. I've tried using the recommended resolutions to Migrate my project
> and they dont work.

Such as? Don't work how?

It'd help if you could post some representative code and the error messages
that you're getting.

Typical problems in porting code from VC6 include:

- Lack of the 'typename' keyword in places where the C++ standard (and
VC7.1+) require it.
- Dependency on the obsolete <iostream.h> version of I/O streams (use
<iostream> instead).
- Dependency on names being in the global namespace that are now (correctly)
in the ::std namespace.

In converting the project itself from VC6 to VC7 or later, the most common
problem is that of compilation options being converted improperly - in
particular, the project conversion has a nasty habit of turning all of your
VC6 per-project options into per-file options in the converted project,
which can be very confusing when you subsequently try to change project
options and find that nothing's changing in your build.

>
> 2. I dont think it is possible to downgrade to Visual C++ 6 from
> Visual C++.net as the downgrade page for this option leads to a dead
> page. Hopefully this is possible however and someone will correct me.

VS6 is still included in MSDN Professional and above, and is still available
for downgrade (although it's no longer supported).

-cd


.

Relevant Pages

  • Re: VC++2005 executables much slower than VC++6????
    ... so your benchmark is very sensitive to the speed of the standard ... the "Secure SCL") that are probably slowing you down. ... Another thing that's changed since VC6 is the use of the small block heap. ... apples to apples (i.e. compile the same code with both compilers), ...
    (microsoft.public.vc.language)
  • Re: Visual Studio 6 vs. .NET 2005
    ... you can download the express edition for free from microsoft: ... support for targetting the .Net framework. ... I would have to disagree with this slamming of VC6. ... I have not had any trouble getting my code so it will compile in both VC6 and VC7.1. ...
    (microsoft.public.vc.language)
  • Re: Convert Access 2 to Access 2000
    ... > Chris are you suggesting I convert first to A97? ... The other responders are all known and highly respected by me. ... > will try to compile the lot. ... converting, is that it's hard nowadays to find programmers familiar with A2.0. ...
    (microsoft.public.access.conversion)
  • Re: How to compile ATL module with CLR
    ... I'm afraid I can't reproduce it right now, since I also don't have VC6 ... Can you point me to instructions of upgrading ATL/MFC code to VC8? ... Following the instructions that I found on MSDN, I only compile stdafx.cpp ... code compiled as manages or as unmanaged code? ...
    (microsoft.public.dotnet.languages.vc)
  • Re: VC++2005 executables much slower than VC++6????
    ... so your benchmark is very sensitive to the speed of the standard ... the "Secure SCL") that are probably slowing you down. ... Another thing that's changed since VC6 is the use of the small block heap. ... apples to apples (i.e. compile the same code with both compilers), ...
    (microsoft.public.vc.language)