Whidbey vs VB.NET 2003

[Guest]

I have NOT yet made the transition from VB 6 to VB.NET 2003. I know some of the general differences, but I'm not yet to the point where I would feel comfortable starting a new project in .NET. At any rate, I was going to get some books and begin learning more about it and try to make the jump, but then I see that Whidbey or VS.NET 2005 will be coming out in the next year or so.

How different is this new release going to be from VB.NET 2003? If I start learning VB.NET 2003, am I just going to have to start over and re-learn everything when VB.NET 2005 is released? Should I just wait

 

[CJ Taylor]

I have NOT yet made the transition from VB 6 to VB.NET 2003. I know some

of the general differences, but I'm not yet to the point where I would feel
comfortable starting a new project in .NET. At any rate, I was going to get
some books and begin learning more about it and try to make the jump, but
then I see that Whidbey or VS.NET 2005 will be coming out in the next year
or so.
Ha. Late 2005. Plenty of time.

How different is this new release going to be from VB.NET 2003? If I

start learning VB.NET 2003, am I just going to have to start over and
re-learn everything when VB.NET 2005 is released? Should I just wait?
Sooner the better. just more classes in 2005, more features, more
streamlined, etc. herfried knows a lot of them (a lot of web oriented
stuff). Your not going to relearn, just learn. =)

-CJ

 

[Scott M.]

I agree with CJ, but just an FYI...

The next version of the .NET Framework is code named "Whidbey".
The next version of the development tool is VS.NET 2005.

It's important to separate the tool from the engine.

 

[CJ Taylor]

Good point. My bad.

I agree with CJ, but just an FYI...

The next version of the .NET Framework is code named "Whidbey".
The next version of the development tool is VS.NET 2005.

It's important to separate the tool from the engine.

 

[Guest]

Great. Thanks for the help. Looks like it time to just dive in and go for it. Pretty sad that I'm so far behind, but you know how that goes


----- CJ Taylor wrote: ----

Good point. My bad

I agree with CJ, but just an FYI..

The next version of the .NET Framework is code named "Whidbey"

The next version of the development tool is VS.NET 2005

It's important to separate the tool from the engine

"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in messag I have NOT yet made the transition from VB 6 to VB.NET 2003. I kno

som
of the general differences, but I'm not yet to the point where I woul fee
comfortable starting a new project in .NET. At any rate, I was going t ge
some books and begin learning more about it and try to make the jump bu
then I see that Whidbey or VS.NET 2005 will be coming out in the nex yea
or so

Ha. Late 2005. Plenty of time
How different is this new release going to be from VB.NET 2003? If

start learning VB.NET 2003, am I just going to have to start over an
re-learn everything when VB.NET 2005 is released? Should I just wait

Sooner the better. just more classes in 2005, more features, mor

streamlined, etc. herfried knows a lot of them (a lot of web oriente
stuff). Your not going to relearn, just learn. =

-C

 

[Phill. W]

The next version of the .NET Framework is code named "Whidbey".
The next version of the development tool is VS.NET 2005.

It's important to separate the tool from the engine.

Scott,

Does that mean we'll finally be able to link-up VS 2005 (the .Net
nonclementure now being "passe" or, at best, "old news" to Our
Friends in Redmond) to /any/ version of the Framework we want,
or are the "tool" and "engine" still hard-wired into one another, as
with VS [.Net] 2003.

Regards,
Phill W.

 

[Brian Henry]

VS2005 is gona be nice, it will allow for cross languge compileing in a
singe project... so you can have J#,C#,VB,C++ files all in a single project
compiled corretly, currently you can only do that across seperate projects.

I have NOT yet made the transition from VB 6 to VB.NET 2003. I know some

of the general differences, but I'm not yet to the point where I would feel
comfortable starting a new project in .NET. At any rate, I was going to get
some books and begin learning more about it and try to make the jump, but
then I see that Whidbey or VS.NET 2005 will be coming out in the next year
or so.

How different is this new release going to be from VB.NET 2003? If I

start learning VB.NET 2003, am I just going to have to start over and
re-learn everything when VB.NET 2005 is released? Should I just wait?

 

[Brian Henry]

actually, next development tool is Visual Studio 2005, .NET has been dropped
from the name

 

[Herfried K. Wagner [MVP]]

I have NOT yet made the transition from VB 6 to VB.NET 2003. I know
some of the general differences, but I'm not yet to the point where I
would feel comfortable starting a new project in .NET. At any rate, I
was going to get some books and begin learning more about it and try to
make the jump, but then I see that Whidbey or VS.NET 2005 will be coming
out in the next year or so.

Did you have a look at the trial version?

<URL:http://msdn.microsoft.com/vstudio/productinfo/trial/>

Install it on a separate system (for example, in Virtual PC, VMware or a
separate PC) and play around with it.

How different is this new release going to be from VB.NET 2003? If I
start learning VB.NET 2003, am I just going to have to start over and
re-learn everything when VB.NET 2005 is released? Should I just wait?

No, there are only some additions to the VB.NET programming language
like generics or operator overloading and some new keywords, but the
main part of the programming language will be the same. VB.NET 2003
code will 99.999...% work unchanged in VB.NET 2005.

I would take a look at VB.NET 2003 now, for example with the trial
version. You can find some tutorials, videos, etc. here:

<URL:http://msdn.microsoft.com/vbasic/vbrkit/>

 

[Herfried K. Wagner [MVP]]

actually, next development tool is Visual Studio 2005, .NET has been dropped
from the name

I didn't notice that yet, but now I took a look at the cover of the CTP
version of VS 2005 and the ".NET" is really missing ;-).

 

[CJ Taylor]

Hmm... Not to contradict, I'm sure your right, but there is misinformation
some where..

http://msdn.microsoft.com/vstudio/whidbey/default.aspx

Visual Studio "Whidbey"
The code name "Whidbey" release of Visual Studio

=)

 

[Guest]

I actually have a MSDN subscription here at work, so I already have the full version and have it installed on my machine. I've played around with it some, but like I told someone else, I don't know enough about it to feel confident in starting new projects in it just yet

That's good to hear that the main part of the language will be the same. I figured that it probably would be pretty similar to .NET 2003, and that the jump from VB6 just to VB.NET itself would be the hardest part. Just wasn't sure

Thanks for the link to the Resource Kit. Looks like it will be helpful. Gonna go download it now


----- Herfried K. Wagner [MVP] wrote: ----

I have NOT yet made the transition from VB 6 to VB.NET 2003. I kno
some of the general differences, but I'm not yet to the point where
would feel comfortable starting a new project in .NET. At any rate,
was going to get some books and begin learning more about it and try t
make the jump, but then I see that Whidbey or VS.NET 2005 will be comin
out in the next year or so

Did you have a look at the trial version

<URL:http://msdn.microsoft.com/vstudio/productinfo/trial/

Install it on a separate system (for example, in Virtual PC, VMware or
separate PC) and play around with it

How different is this new release going to be from VB.NET 2003? If
start learning VB.NET 2003, am I just going to have to start over an
re-learn everything when VB.NET 2005 is released? Should I just wait

No, there are only some additions to the VB.NET programming languag
like generics or operator overloading and some new keywords, but th
main part of the programming language will be the same. VB.NET 200
code will 99.999...% work unchanged in VB.NET 2005

I would take a look at VB.NET 2003 now, for example with the tria
version. You can find some tutorials, videos, etc. here

<URL:http://msdn.microsoft.com/vbasic/vbrkit/

 

[Scott M.]

Actually, the tool and the framework aren't as "hard-wired" as you may
think.

It is entirely possible (today) to have an application built with VS .NET
2002 run on the 1.1 Framework and have an application built with VS .NET
2003 run on the 1.0 Framework. This capability is not built into the IDE
however. But, I have seen several free utilities that will change what
version of the Framework a .NET application "targets".

The next version of the .NET Framework is code named "Whidbey".
The next version of the development tool is VS.NET 2005.

It's important to separate the tool from the engine.

Scott,

Does that mean we'll finally be able to link-up VS 2005 (the .Net
nonclementure now being "passe" or, at best, "old news" to Our
Friends in Redmond) to /any/ version of the Framework we want,
or are the "tool" and "engine" still hard-wired into one another, as
with VS [.Net] 2003.

Regards,
Phill W.

 

[Phill. W]

Scott,

It is entirely possible (today) to have an application built with VS
.NET 2002 run on the 1.1 Framework and have an application built
with VS .NET 2003 run on the 1.0 Framework.

Are there not "compatibility" problems with some parts of the
Framework's internals? (ISTR Securitybeing one of them).
Are there /going/ to such problems with the release of Framework 2.0?

This capability is not built into the IDE however.

And therein lies my probelm. The IDE is [probably] capable of being
version independent and using whatever version it is asked to, it's just
that Our Friends in Redmond haven't got around to taking that final
step - if for no other reason than they'd sell a lot less 'Studio upgrades
;-)

Regards,
Phill W.

 

[Herfried K. Wagner [MVP]]

Are there not "compatibility" problems with some parts of the
Framework's internals? (ISTR Securitybeing one of them).

There are at least problems if you are using classes of .NET 1.1 which
are not available in .NET 1.0.

Are there /going/ to such problems with the release of Framework 2.0?

I don't know, but the framework will grow, so it's more likely to use a
class which is new in .NET 2.0 and not available in the older versions
of the framework.

This capability is not built into the IDE however.

And therein lies my probelm. The IDE is [probably] capable of being
version independent and using whatever version it is asked to, it's just
that Our Friends in Redmond haven't got around to taking that final
step - if for no other reason than they'd sell a lot less 'Studio upgrades
;-)

The update VS.NET 2002 -> VS.NET 2003 was available for USD 31 for about
half a year after VS.NET 2003 was released. Microsoft even provided a
way to run both, VS.NET 2002, and VS.NET 2003 on the same machine.

 

[Chris Dunaway]

And therein lies my probelm. The IDE is [probably] capable of being

version independent and using whatever version it is asked to, it's just
that Our Friends in Redmond haven't got around to taking that final

I agree completely. I've never understood why they didn't de-couple the
..Net framework from the IDE. The IDE should be able to scan the system and
use whatever framework is available. If multiple frameworks are installed,
then it should be able to handle that.