Changes from VS 6 to VS NET 2003

[Hero]

I thinks the best answer is that there is nothing similar between these two versions!
Because in VS 2003 .NET,the VS is became behind an layer named .NET framework
and every program is written for this layer language(Don't look it the apperance
of language that compiled code in deferent.)
This is theoricaly for making VS 2003 .NET portable between deferent OSs.
VS 2003 .NET is compiling to MSIL(Microsoft Intermediate Language) but the earlier
versions will be compiled for system OS direcly(asmbelly language).
If somebody want to work with OS basic structures,Normaly should use VS 6 because
It is more powerfull than VS 2003 .NET for working with system.

sincerely yours

[FEARHQ]

VS.NET can perfectly well produce native PE files just fine, thanks. Vc.NET has nothing to do with .NET

A difference I did notice is that you now must use the
#pragma comment(lib, "libname")
to include any library else linker will fail. That's probably what's messing you up

[ArC]

A difference I did notice is that you now must use the
#pragma comment(lib, "libname")
to include any library else linker will fail. That's probably what's messing you up

You can specify the libraries to use in the linker configuration tab. See the attachment.

And as FEARHQ already said, VC++ .NET can produce native win32 apps. Of course this depends on which components you install. If you only install Visual C# or Visual Basic .Net you can only produce .NET apps

In VS .NET they also updated MFC from 4.x to 7.x.. 7.x for instance supports HTML dialogs.

The debugger was improved. DLL debugging has become a bit easier.

Also is there any commands to add or omit to make it compile most like VS 6 and less for .NET Standards. A lot of my code that worked before now no longer works with .NET 2003.

To make your code compatible at first you should look what problems the compiler/linker has (e.g. are there libraries/header files missing, does the compiler have problems with certain expressions, ....). Missing libraries/header files can possibly be fixed in short time. Same goes for certain errors during compilation. Anyways if you get errors like INTERNAL COMPILER ERROR or sth it can get a bit more complicated.

Originally Posted by ArC

You can specify the libraries to use in the linker configuration tab. See the attachment.

And as FEARHQ already said, VC++ .NET can produce native win32 apps. Of course this depends on which components you install. If you only install Visual C# or Visual Basic .Net you can only produce .NET apps

In VS .NET they also updated MFC from 4.x to 7.x.. 7.x for instance supports HTML dialogs.

The debugger was improved. DLL debugging has become a bit easier.

To make your code compatible at first you should look what problems the compiler/linker has (e.g. are there libraries/header files missing, does the compiler have problems with certain expressions, ....). Missing libraries/header files can possibly be fixed in short time. Same goes for certain errors during compilation. Anyways if you get errors like INTERNAL COMPILER ERROR or sth it can get a bit more complicated.

So do I just open up a project and set those settings and expect it to work. Is there any places where I have to say ... "no.. not .NET .... its Win32"?

Thanks. I'm accustomed to using VS 6 but I'm trying to get over to the .NET 2003 IDE.

[ArC]

Originally Posted by joejoejoe

So do I just open up a project and set those settings and expect it to work. Is there any places where I have to say ... "no.. not .NET .... its Win32"?

If you convert a VC++ 6.0 project to VS .NET it is automatically configured to produce native Win32 apps.
If you create a completely new project you have to choose which type of project you want to create. If you decide to create a Visual C# project the output will be a .NET executable. A Visual C++ project will produce native Win32 apps whereas those projects can be configured to use the .NET framework, too. But even in that case it should still produce native apps.

I had no trouble converting VS6 projects/workspaces to VS.NET2003 solutions except for the C++ language compliance issues.

Some time ago I compiled a project with VS .NET 2003 and I encountered an INTERNAL COMPILER ERROR. The same project compiles just fine with VC++ 6.0 + latest SP + Processor Pack.