473,503 Members | 2,148 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Whidbey vs VB.NET 2003

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

Nov 20 '05 #1
14 1413

"dlangell" <an*******@discussions.microsoft.com> wrote in message
news:0F**********************************@microsof t.com...
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
Nov 20 '05 #2
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 message
news:%2****************@TK2MSFTNGP12.phx.gbl...

"dlangell" <an*******@discussions.microsoft.com> wrote in message
news:0F**********************************@microsof t.com...
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

Nov 20 '05 #3
Good point. My bad.

"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:eI**************@TK2MSFTNGP09.phx.gbl...
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 message
news:%2****************@TK2MSFTNGP12.phx.gbl...

"dlangell" <an*******@discussions.microsoft.com> wrote in message
news:0F**********************************@microsof t.com...
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


Nov 20 '05 #4
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

"Scott M." <s-***@BADSPAMsnet.net> wrote in messag
news:eI**************@TK2MSFTNGP09.phx.gbl..
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 news:%2****************@TK2MSFTNGP12.phx.gbl.. "dlangell" <an*******@discussions.microsoft.com> wrote in messag

news:0F**********************************@microsof t.com..
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
>>

Nov 20 '05 #5
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:eI**************@TK2MSFTNGP09.phx.gbl...
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.
Nov 20 '05 #6
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.
"dlangell" <an*******@discussions.microsoft.com> wrote in message
news:0F**********************************@microsof t.com...
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?

Nov 20 '05 #7
actually, next development tool is Visual Studio 2005, .NET has been dropped
from the name ;)
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:eI**************@TK2MSFTNGP09.phx.gbl...
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 message
news:%2****************@TK2MSFTNGP12.phx.gbl...

"dlangell" <an*******@discussions.microsoft.com> wrote in message
news:0F**********************************@microsof t.com...
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


Nov 20 '05 #8
* "Brian Henry" <br**********@newsgroups.nospam> scripsit:
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 ;-).

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
Nov 20 '05 #9
* "=?Utf-8?B?ZGxhbmdlbGw=?=" <an*******@discussions.microsoft.com> scripsit:
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]
<URL:http://dotnet.mvps.org/>
Nov 20 '05 #10
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

=)

"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:eI**************@TK2MSFTNGP09.phx.gbl...
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 message
news:%2****************@TK2MSFTNGP12.phx.gbl...

"dlangell" <an*******@discussions.microsoft.com> wrote in message
news:0F**********************************@microsof t.com...
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


Nov 20 '05 #11
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: ----

* "=?Utf-8?B?ZGxhbmdlbGw=?=" <an*******@discussions.microsoft.com> scripsit
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/

--
Herfried K. Wagner [MVP
<URL:http://dotnet.mvps.org/>
Nov 20 '05 #12
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".
"Phill. W" <P.A.Ward@o-p-e-n-.-a-c-.-u-k> wrote in message
news:c6**********@yarrow.open.ac.uk...
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:eI**************@TK2MSFTNGP09.phx.gbl...
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.

Nov 20 '05 #13
* "Phill. W" <P.A.Ward@o-p-e-n-.-a-c-.-u-k> scripsit:
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).


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.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
Nov 20 '05 #14
> 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.

--
Chris

To send me an E-mail, remove the underscores and lunchmeat from my E-Mail
address.
Nov 20 '05 #15

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

1
282
by: mosquitooth | last post by:
H is there any way to use the new cool WinBar (etc.) controls of studio Whidbey in the current version (2003) of the studio Thank mosquitooth
1
1252
by: Steven Spits | last post by:
Hi, I've been playing with ClickOnce on Whidbey. Looks easy to deploy apps on your clients. It generates .deploy files, which can only be interpreted by the machine we installed Whidbey on. ...
0
1338
by: Cave | last post by:
Is there a way to install the SQL Reporting Services Client on Whidbey ? The installer searches the system for an installation of Visual Studio 2003 in order to install the client part of SQL RPS....
2
1497
by: Wernfried Schwenkner | last post by:
On my machine (W2003) I had Sharepoint portal server running, just the default settings after setup together with .NET 2003. Now I tried out to install Whidbey. Thenafter the Sites from SPPS...
1
356
by: marcus | last post by:
I actually honestly believe that this problem might stem from my SQL 2005 Express installation, but since it occurs in Whidbey I figured I'd post here. My problem is that I can't create a new...
0
915
by: RedSherlock | last post by:
Is there a built in value I can use in a "#if . . ." clause to determine if I'm compiling in VS.Net Whidbey? The compiler is complaining about a few API calls that are valid and legal in VS.Net...
3
1312
by: mt | last post by:
Where can I access the Page_Load event in Whidbey for a C# ASP.NET website? Since the partial class has been introduced, I'm not sure where I should be putting page load events. Thanks very...
4
1273
by: howard dierking | last post by:
I am running windows xp with both vs2003/.net 1.1 and the whidbey/.net 2.x beta 1. Since i installed whidbey, i have been able to neither run (F5) my apps nor attach to the aspnet worker process...
4
1229
by: Bob Garbados | last post by:
We have some 1.1 sites developed in dreamweaver and we will be developing all new sites for the 2.0 framework when it's out of beta. We just purchased an ms subscription and will be using visual...
0
7205
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
0
7093
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
0
7287
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers,...
1
7011
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
0
7468
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
1
5023
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new...
0
3170
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
1
747
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.
0
401
bsmnconsultancy
by: bsmnconsultancy | last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.