There are two really big differences from my
perspective. The first is only if you did any
development in VB 6.0 and that is the upgrade wizard.
Secondly, the Standard VB.Net only allows connections to
Access DBs, not good if you want to make an app for SQL
server.[color=blue]
>-----Original Message-----
>Hi there,
>[color=green]
>> I'm currently using Visual Studio .Net 2002 Academic.[/color][/color]
I'm considering[color=blue][color=green]
>> purchasing VB.Net 2003. Besides the additional[/color][/color]
languages what else is[color=blue][color=green]
>> specific to VS.Net that wouldn't be included in just[/color][/color]
VB.Net?[color=blue]
>
>If you just want to develop with VB.NET, just buy[/color]
VB.NET. Ignore all of the[color=blue]
>information stating that you should buy VS.NET if you[/color]
are a professional,[color=blue]
>because that is absolute boll*cks.
>
> *VS.NET contains the other Microsoft .NET languages,[/color]
which have no[color=blue]
>relevance to VB.NET
> *VS.NET contains the VB6 upgrade wizard if you are[/color]
planning on upgrading[color=blue]
>VB6 code to VB.NET, this *may* come in handy
> *VS.NET contains some server components which are[/color]
useful if you plan on[color=blue]
>developing ASP.NET applications on a server other than[/color]
localhost. Such as[color=blue]
>another computer in you LAN.
> *VS.NET contains the crystal repots objects, not[/color]
available in the[color=blue]
>componentized versions alone.
>
>You can use VB.NET with Windows XP Home edition but you[/color]
cannot develop[color=blue]
>ASP.NET applications on localhost as it does not have[/color]
IIS installed, but you[color=blue]
>can develop from XP Home onto an XP Pro system for[/color]
example, or any other[color=blue]
>Windows OS that has IIS installed.
>[color=green]
>> For example: Would I notice a difference in features[/color][/color]
if I was just[color=blue][color=green]
>> developing Windows Forms Apps? Are the database[/color][/color]
wizards and server[color=blue]
>explorer[color=green]
>> in both? Etc.[/color]
>
>Nope, they are idential, you don't get all the templates[/color]
though, that is one[color=blue]
>downside. Initially it will look like you can't develop[/color]
things such as[color=blue]
>Windows Services and Class Libraries, but in fact you[/color]
can, you need to[color=blue]
>change the project files manually with notepad to do[/color]
so. Or, get the[color=blue]
>templates!
>
>I am set firm on these beliefes as I had the 2nd beta of[/color]
VS.NET and didn't[color=blue]
>use anything other than VB.NET anyway. I have VB.NET[/color]
now and don't need[color=blue]
>anything else, hence an upgrade would be totally[/color]
pointless for me unless I[color=blue]
>wanted to learn C#, or one of the other languages whilst[/color]
retaining the IDE.[color=blue]
>
>Ask yourself that main question, do you only want to use[/color]
VB? If so just buy[color=blue]
>VB, unless you want all of the other stuff that comes[/color]
with VS.NET, such as[color=blue]
>the ones mentioned above.
>
>Nick.
>
>This link is the a web page that contains all of the[/color]
other templates for[color=blue]
>VB.NET, the ones that are missing. It just shows that[/color]
it is possible to do[color=blue]
>without ANY errors in the slightest, but this is only[/color]
for version 2002 as[color=blue]
>that is all I have at the moment until I upgrade to 2003.
>
http://members.lycos.co.uk/nickpatem...oft-vbtemp.htm
>
>--
>/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/[/color]
\/\/\/\/\/\/\/\/\/\[color=blue]
>"No matter. Whatever the outcome, you are changed."
>
>Fergus - September 5th 2003
>/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/[/color]
\/\/\/\/\/\/\/\/\/\[color=blue]
>
>
>.
>[/color]
