VB.NET - 2002 vs. 2003

[TB]

I have just recently started to migrate towards .NET (have been working with
a solid classic ASP and VB6 foundation) and have just installed Visual
Studio.NET (2002). We have not purchased VS.NET 2003, and I'm wondering if
it's necessary.

Are there any major changes in 2003 that warrant me postponing new
development in .NET until we upgrade?

[Cor Ligthert]

TB,

I have just recently started to migrate towards .NET (have been working with a solid classic ASP and VB6 foundation) and have just installed Visual
Studio.NET (2002). We have not purchased VS.NET 2003, and I'm wondering if
it's necessary.

Are there any major changes in 2003 that warrant me postponing new
development in .NET until we upgrade?

There are a lot however to give you one,

The upgrading part from VB6 to VBNet in VB2003 is much better than in
VB2002.

Better newsgroups to ask this question are
official however almost dead
microsoft.public.dotnet.languages.vb.upgrade
and better
microsoft.public.dotnet.languages.vb

I hope this helps?

Cor

[Norman Yuan]

The difference basically does not lie in the VB.NET language (2002 or 2003).
It is the .NET framework that makes differences. VS.NET2002 only works with
..NET framework 1.0, while 2003 is with framework1.1 (and also can work with
1.0). If your app's users have not put .NET framework on, when it is time to
load .NET framework, it would be better go with 1.1, rather than 1.0 for
them. In that case, to run your app, they still have to load 1.0.

"TB" <[e-mail]> wrote in message
news:D3**********************************@microsof t.com...

I have just recently started to migrate towards .NET (have been working with a solid classic ASP and VB6 foundation) and have just installed Visual
Studio.NET (2002). We have not purchased VS.NET 2003, and I'm wondering if
it's necessary.

Are there any major changes in 2003 that warrant me postponing new
development in .NET until we upgrade?