Microsoft visual studio

This is a discussion on Microsoft visual studio within the A Brief History of Cprogramming.com forums, part of the Community Boards category; I'm using Visual C++ version 6 right now, but I also have Visual studio Dot Net (version 7) on cd. ...

Microsoft visual studio

I'm using Visual C++ version 6 right now, but I also have Visual studio Dot Net (version 7) on cd. A friend told me I can stay with Visual C++ ver 6, but what do you think? Shall I stay with v.6 or go to v.7?

I'm using Visual C++ version 6 right now, but I also have Visual studio Dot Net (version 7) on cd. A friend told me I can stay with Visual C++ ver 6, but what do you think? Shall I stay with v.6 or go to v.7?

Well, version 7 sucks less than version 6. If you can manage to get an upgrade to .NET 2003 (version 7.1) get that -- 7.1 is an incredibly good compiler. 7 is only okay, but better than 6.

.NET 2005 is excellent. 2003 is also good. You'll be converted simply by using either one. It took me about 1/2 an hour to fall in love. There's a little BS to get used to but hey, thats the way it is in any new relationship.

I got VS6.0 and VS.Net 2003 both on my machine. After I installed 2003 I hardly find myself launching VC++ 6.0 anymore and if I do it by "accident" (you know, when youre too tired in the morning and only reflexes are operational) my first thoughts are "what is this ........"?

Just install .net, it doesnt break your old vc installation (atleast it did not do it to me) and see for yourself

I haven't made the switch yet. Probably for the same reason that I haven't stepped foot inside a McDonalds for over 15 years now...

Superstition. (Well, the McDonalds thing was due to being served a soggy burger when I was young and impressionable)

In most cases I like to target all Windows platforms, including Windows 95. Some of these are incompatible with the .NET platform, so I wouldn't like to introduce code changes that would rule those targets out.

That's not to say that I wouldn't wanna use it, I mean, given that Windows is supposedly going to move to a situation where .NET code is ran "natively" and unmanaged code is ran in some sort of managed VM.