switching to C++.NET?

[kodeguruguy]

I currently use c++ 6.0 and I'm thinking about starting to use c++.NET but I'm curious to know a few things before I purchase the package. I know the .NET adds garbage collector and many other things, but what I really want to know is, would I still be able to do the same type of programming I did in c++ 6.0? By that I mean, is the script fairly the same, or is it a totally different world in .NET? Could I for example go through the wizard and create the base code for an SDI application, and if I can, would it be almost identical to the code that was created in c++ 6.0?

In other words, would I be able to compile an application that was created in c++ 6.0 in the .NET enviornment without having to make to many changes?

Thanks for your adivse in advance. :thumb:

[Chris Green]

yes, similar, sorta, yes

go ahead and get on board, no need to worry about backwards compatibility and you can have vc6 installed at the same time.

[kodeguruguy]

Thanks for the advice. I'm glad somebody replied.

[Andreas Masur]

I currently use c++ 6.0 and I'm thinking about starting to use c++.NET but I'm curious to know a few things before I purchase the package. I know the .NET adds garbage collector and many other things, but what I really want to know is, would I still be able to do the same type of programming I did in c++ 6.0? By that I mean, is the script fairly the same, or is it a totally different world in .NET? Could I for example go through the wizard and create the base code for an SDI application, and if I can, would it be almost identical to the code that was created in c++ 6.0?

In other words, would I be able to compile an application that was created in c++ 6.0 in the .NET enviornment without having to make to many changes?

Well...this kind of question have been asked several times, thus, searching the forums will bring up some threads.

Nevertheless, .NET comes with a new MFC dll, thus, in general the applications would be the same, however, there might be slight differences. Due to this, you might need to make changes to an application created with 6.0 before it compiles with the .NET compiler...

[kodeguruguy]

Thanks. :thumb:

[Mutilated1]

In my experience porting MFC applications from VC6 to VC.NET is as simple as a rebuild. A couple of ATL/WTL applications were a little harder to upgrade, but not nearly as hard as upgrading ATL applications was a few years ago when we upgraded from VC5 to VC6. VC.NET is a very nice development environment, but its not really worth the price for the upgrade unless you are going to do .NET development. You don't have to do .NET with the new compiler because you can still build regular old "unmanaged" applications like you could before, but in that case there is really no reason to get the new compiler.