Transition from VB6.0 to VB .NET

[dbelley_office]

I wanted to see the pricing information on VB 6.0 but it seems I have to go
with Visual Basic .NET now.

I've been developing for 4-5 years with VB 6.0.
I have a project to do so I had to buy VB 6.0 for that particular customer.
I was wondering if for me .. a VB 6.0 developer it would be a rough
transition to go with VB .NET? I won't develop a web-application this time.
Only an application using SQL Server as database, no web transaction.

I don't want to be too slow and take 2 month for a usual 1-month project.

Thanks for giving me your personnal feeling on the transition between the 2
developement tools.

Should I go and buy Visual Studio .NET even if it costs a little more ... of
for me ACTUALLY doing only VB stuff ... VB.NET is enough.

[Mike Ryan]

Hello,

I was wondering if for me .. a VB 6.0 developer it would be a rough
transition to go with VB .NET?
I don't want to be too slow and take 2 month for a usual 1-month
project.
I'd guess that transitioning from VB to VB.NET will take at least that
long to get started, so give yourself plenty of time so you don't get burnt!

Are you familiar with object-oriented programming? Any knowledge of that
topic will be helpful. There's the syntax to learn, which isn't much
different from what you've been doing, and then of course there's the
..NET Framework Class Library itself.

If you've been developing Windows applications it's probably a good idea
to go the WinForms route instead of WebForms as you suggested, at least
initially.
Should I go and buy Visual Studio .NET even if it costs a little more ... of
for me ACTUALLY doing only VB stuff ... VB.NET is enough.

I guess that'll depend on your requirements. If it's only a little more
then it certainly makes sense to do so.

Good luck!

- Mike

[Cor Ligthert]

Hi,

It is not always an easy step.

C# and VBNet are more look alike than
VB6 and VBNet

I have seen in the language.vb newsgroup that there are expirienced VB6
programmers (including MVP's) who have very much problems with VBNet, while
there are others who learn it on the fly (and than never want to go back to
the classic VB way).

About your question from VBNet and VSNet, as you describe it would as far as
I can see VBNet be enough for you. As far as I can see you do you exclude
everything for what VSNet should be needed.

Just my idea

Cor

[Paul Clement]

On Tue, 25 Jan 2005 09:48:12 +0100, "Cor Ligthert" <no************@planet.nl> wrote:

¤ Hi,
¤
¤ It is not always an easy step.
¤
¤ C# and VBNet are more look alike than
¤ VB6 and VBNet
¤
¤ I have seen in the language.vb newsgroup that there are expirienced VB6
¤ programmers (including MVP's) who have very much problems with VBNet, while
¤ there are others who learn it on the fly (and than never want to go back to
¤ the classic VB way).
¤
¤ About your question from VBNet and VSNet, as you describe it would as far as
¤ I can see VBNet be enough for you. As far as I can see you do you exclude
¤ everything for what VSNet should be needed.

It depends a lot upon your perspective. Sure there are some Classic VB developers who seem to
believe that VB.NET is a different language. It's also incorrect because a high percentage of the
core language is still intact. The reason they say they're completely different languages is because
of the difficult of porting Classic VB extensions to their .NET counterparts. This is not primarily
a language issue - it's a framework issue.

In any event I am still a Classic VB developer but having now worked with both, and taken many of my
skills from Classic to .NET, I have to shake my head every time someone says they're different
languages.

The only significant aspect that VB.NET and C# share is the .NET framework. The languages are quite
different with respect to syntax and core language components.
Paul ~~~ pc******@ameritech.net
Microsoft MVP (Visual Basic)

[Cor Ligthert]

Paul,

I was refering to a thread by some classic VB programmers recently made in
the language.vb newsgroup. I see now that you were as well active in that
thread, I did not mean you by the MVP's I stated in my previous message in
this thread. You are not talking like that in that thread, moreover, I
remember me a very recently message from you which is in oposite of that.

I did not say in my previous message that the language differs, however the
good use of the language is in my opinion more as C# than in as VB6. I
always write that in dotNet the program languages are only the glue to makes
to program using the dotNet classes.

I hope this clears what I want to say

Cor

[Paul Clement]

On Tue, 25 Jan 2005 16:31:50 +0100, "Cor Ligthert" <no************@planet.nl> wrote:
¤ I was refering to a thread by some classic VB programmers recently made in
¤ the language.vb newsgroup. I see now that you were as well active in that
¤ thread, I did not mean you by the MVP's I stated in my previous message in
¤ this thread. You are not talking like that in that thread, moreover, I
¤ remember me a very recently message from you which is in oposite of that.
¤

Cor,

Keep in mind my last post in the thread to which you are referring (to alpine) was essentially
sarcastic. Sometimes it's the only way to respond to the nonsense posted by some Classic VB
developers.

There is nothing in that thread which indicates that I believe the languages are completely
different. I don't.

¤ I did not say in my previous message that the language differs, however the
¤ good use of the language is in my opinion more as C# than in as VB6. I
¤ always write that in dotNet the program languages are only the glue to makes
¤ to program using the dotNet classes.
¤
¤ I hope this clears what I want to say

That's fine. I wasn't speaking to what you said specifically. My comments were in reference to
discussions I've had with other VB developers and their opinion that VB.NET is a language that is
completely different than Classic VB.

I don't know what your background is with respect to Classic VB (or whether you've actually used it
before) so I can't make any judgements as far as your statements are concerned.

If you're simply repeating statements from Classic VB developers then all I'm trying to do is
dispell another myth.
Paul ~~~ pc******@ameritech.net
Microsoft MVP (Visual Basic)