VC6 and MSDN compatibility

[Will2]

Hello guru,

I' been away a little while from doing the fun thing of coding, and have a chance to return. My questions are about setting up an environment (I wish to stay with VC6 for now):
Q. What is the latest MSDN I should install, someone told me Oct 2001 release?
Q. What is the latest SDK to use.
Q. Any tips on installing the old thing (VC6 I mean) are much appreciated.

My main concern is compatibility because I heard someone has to wrestle with his system after mixing VC6 and VC.NET. Thank you very much.


Will

[voidspace]

You would need to install VC6 first. And also the service pack 5 for VC6.

Then MSDN Oct 2001 ( On the CD it is written if it can be used or not)

[astanley]

You can use an MSDN later than Oct 2001, it just won't be integrated into the IDE. But it will have the latest articles (including a lot of .Net stuff, which you probably don't want).
I find Oct 2001 OK for most things.

You can use the latest platform SDK (download from Microsoft) with VC6.

[Will2]

Hi,

Thanks for the tips, and most likely great time saver too.

May I just pump in a few side questions:
Q. Can I use VC.NET as VC6; to do MFC stuff etc.?
Q. Could any one point me to an article comparing the two? I have a feeling I don't need .NET if I don't do Internet stuff, is it right?


Will

[astanley]

Q. Can I use VC.NET as VC6; to do MFC stuff etc.?

Definitely yes. The C++ compiler is more standard conformant too. It is relatively simlpe to port C++ and MFC programs from VC6 to VC .Net (unmanaged C++ code - runs outside of .Net environment, i.e., just like a traditional Windows C++ program).

In .Net you can also write managed C++ code, which means it runs entirely in the .Net environment.

There have been major changes in VB between VC6 and .Net. VB .Net is managed code only., which makes porting much more difficult (although there are wizards to help with this).

Q. Could any one point me to an article comparing the two? I have a feeling I don't need .NET if I don't do Internet stuff, is it right?

I don't know of any articles - try a google search. The main thing you can do in .Net that you can't in VC6 is write managed code, i.e., use the new .Net languages (C#, VB .Net etc etc). The MFC is pretty similar between the two (Microsoft are not developing it much these days).

You can do "Internet stuff" in both .Net and VC6; this is one area that has changed quite a bit (e.g., in the development of ASP pages).

[Will2]

Many thanks astanley,

I heard many bad stories about VC.NET 6 months ago making me nervous to jump into VC.NET. I feel happier with C++, no disrespect to VB folks.

I've worked with VC6. I could image using VC.NET as a better standard compliance compiler to start off (with unmanaged code - as you described). You're right that VC6 can also do Internet stuff, my impression with the press release is VC.NET is all about Internet development and not conventional windows app. I might be totally wrong.

I’ve invested quite a bit on books and time etc. on VC 6, do I have to go thro’ the same drill for VC.NET – if only to do conventional windows apps. with Win32, MFC, ATL etc.? Again, your view is very much appreciated.


Will

[astanley]

I've been a bit peeved at Microsoft's emphasis with .Net on development Internet based applications (Windows services etc), but rest assured, all the support for traditional desktop application development is still there, including in the .Net languages.

In some respects developing a desktop application (or "thick" client) in .Net languages (C#, VB .Net) is easier, with better integration between the Visual aspect (designing forms) and the underlying code.

All the stuff you've learnt about Win32, MFC and ATL is definitely not wasted - most of this works as before (as unmanaged = not .Net code). There is a bit of a learning curve getting use to the new sexy IDE, but this is not a big problem. I think a background in C++ based Windows development is an advantage to someone coming to .Net, compared to e.g., a traditional VB developer, as we have a much better understanding of what's going on under the hood (so let's all pat ourselves on the back ).

[voidspace]

One thing you will surely miss is the class wizard.

I use both vc6 & vc.net. I build projects in vc6 and finally verify in vc.net. VC.Net is more strict in checking for compilation errors.

[Will2]

Thanks.

Are there any 'cotchas' to avoid when setting up a dual dev. environment?


Will

[Andreas Masur]

Originally posted by Will2
Are there any 'cotchas' to avoid when setting up a dual dev. environment?

Nope...other than the common rule, that you should install the older version first...

I have both VC 6.0 and .NET 2002 running on the same machine without any problems...