Visual Studio 6.0 vs Visual Studio .Net

[BlueAdept]

I currently have VS 6.0, but was just offered VS .net for a real good price from a friend. His company bought it, and was majorly disappointed in it. He said he likes VS 6.0 a lot better.

I would like to know your opinions. Should I dump VS 6 or stay with it and why.

Also, does anyone know if VS .net has that manditory registration? If so, how do I go about changing it over to my name and would MS allow you to change it if it has been registered? I would have a bill of sale.

One more question...why does Microsoft have to be such a pain in the ass with this manditory registration crap? I really dont like giving MS any of my information. I trust them about as far as I could throw them.

[high_jeeves]

I personally prefer .NET, but cant give any real solid reasons as to why.. I do alot of DX stuff, and the integrated shader debugger and better DX symbol tables are nice.



Also, does anyone know if VS .net has that manditory registration? If so, how do I go about changing it over to my name and would MS allow you to change it if it has been registered? I would have a bill of sale.


Nope.. no mandatory reg. or dial home..

--Jeeves

[SeqTester]

I thought that all of them but EA needed to be activated? I could be wrong being I have nto played with this since it was BETA. I used to work in nextgen developer technologies at my last customer.

But I could be wrong that was long ago and I leaving for hunting so no time to look it up, sorry. :(

Figures, I did not get my ShowBuck running with decode yet for my GPS :( ...... Oh welll maybe for next season.

[BlueAdept]

I dont know if it has that mandatory registration or not. It might since it came out in the genera of win2k, sp1, office 2k, office xp, and xp. Those are all mandatory.

That to me is another factor. I really dont want to give MS my info.

[qflux]

I Have VS.Net Enterprise edition and I did not have to activiate it, only thing i need was my key code for it

[z26o]

I have VS.NET Pro - No mandatory registration. Just the key from the disk.

-z-

[SurfAngel]

I have both VB6 and VB.NET installed. (Yes, they co-exist.)

VB.NET has a totally new library and most (I mean most) legit WINAPI calls from pre-.NET will not even compile. IMO, it has a very steeper learning curve. I use both.

[BlueAdept]

Thanks everyone for the help.

I think Ill just stick with the VS 6.0.

Maybe the reason why my friend didnt like .net was because of the new library. Heh...I should buy it and put it up on ebay :). I could make a healthy profit from it, but then again, I would probably lose my friend if he found out ... so I wont take the chance.

[falkore]

Originally posted by SurfAngel
I have both VB6 and VB.NET installed. (Yes, they co-exist.)

VB.NET has a totally new library and most (I mean most) legit WINAPI calls from pre-.NET will not even compile. IMO, it has a very steeper learning curve. I use both.

Yup. I learned (college) on VB6, when I started doing c# stuff and Cross-compiler craps, I thought that I would uninstall my VS6 and just use VS.NET. Well, Almost 0 of my older VB6 stuffs work anymore...


Hi-ho, hi-ho It's off to reinstall MSDN and VS6 I go........<insert whistle>