Printable View
Here are a couple of questions from somebody that wants to switch from VB6.0 to VB.NET....
1. Which version of VB.NET should I use?
2. Can it be installed and not interfere with VB6.0? I have
a lot of VB6.0 applications that I don't want to break by
installing Visual Studio.NET......
... Anything else I should know ...
Thanks.....
1) Use the VS 2003 professional version
2) Yes, 100% absolutely.
I agree with nemaroller on both counts.
I have VB.net standard + VB6 at home on my laptop and they both work fine (even running simultaneously) and VS pro 2003 at work (aren't I a lucky boy?:D).
I must say that VS pro is much better because you get C#, C++ and J++ included not to mention ASP.net.
VB.net standard is a bit drab in comparison but it gets the job done. The price is the only problem with vs.net, but for what it is its good value imo.
If you are going to use it at work then you can spread your work over more than one programming language. This makes you indespensible to your department, and ensures job security :lol:.
Thanks for the replies!
Anyone know the difference between
Visual Studio .NET 2003 Enterprise Architect
Visual Studio .NET 2003 Enterprise Developer
Visual Studio .NET 2003 Professional
... I am in the MSDN program so I can use either, just don't know which would be better to install...:)
I'm using Visual Studio .NET 2003 Enterprise Architect. It's got all the bells and whistles.
This page shows it to be the top of the hill in the VS.NET lineup.
Enterprise Architect is the one you want to install if you have access to them all.
Let's be realistic, who could afford that version if they weren't working for a company that was paying for it?
Quote:
Originally posted by MrGTI
I'm using Visual Studio .NET 2003 Enterprise Architect. It's got all the bells and whistles.
This page shows it to be the top of the hill in the VS.NET lineup.
Wow, I have VS.net 2003 EA and I didnt even know what all it could do. By the way... nobody is paying for my VS.
James
Nobody except the rest of us. :(Quote:
Originally posted by JAtkinson
By the way... nobody is paying for my VS.
James
That was the point, he said he had access to all, which means his company (or him) had a MSDN subscription. That is why I said install EA.Quote:
Originally posted by nemaroller
Let's be realistic, who could afford that version if they weren't working for a company that was paying for it?
Ah... didn't see his follow up post... ;)