VB6 vs. VB.net (a matter of opinion?) 1

[x508]

Hi....please can you provide some opinions.

I am enjoying working on VB6.0 and I have not really come across anything that I could not do in VB6. Should I take up the time, start from scratc and get into VB.net or can I continue using 6 as long as it servers it's purpose?

**********************************
May the Code Be With You...
----------
x50-8 (X Fifty Eigt)

 

[TheTuna]

Remember RPG, ADA, COBOL, FORTRAN, etc?

Sooner or later, our beloved VB6 will be on the list of 'nearly' never used languages. No, I'm not saying any of those languages listed above are not used, but simply not as much.

To ignore .net is to ignor the future. If you're writing code or developing applications for a living, I would definately say LEARN vb.net!

No Dolphins were harmed in the posting of this message... Dolphin Friendly Tuna!

 

[matzos]

I'm kind of in the same boat as x508. Any thoughts on where/how the best method of learning vb.net would be? Is there a good booko to read? An online class to take? Any thoughts would be appreciated.

 

[LochDhu]

I think the question to ask yourself is: What am I going to be doing in 5 years? That is, will you be an 8 hour a day programmer, or possibly move on to project management or something where you will not be programming as a full time duty. MS has committed to supporting VB6 through 2008 - and with the thousands of VB5/6 apps out there, there will certainly be a need for developers to maintain these.

If you are just starting programming or know you will be programming for more years to come then it would be wise to look at .NET - my suggestion for VB6 programmers would be to look at C# first. You can always fall back on VB.NET.

As far as books - there's 100's of them - do a search on Amazon.com and you will find everything you need.

That's my 2 cents worth.

Scott

 

[x508]

Will I be able to install VB.net on the same OS on which my VB6 is installed?

Won't I experiece a problem with .NET extensions or something like that when using VB6

**********************************
May the Code Be With You...
----------
x50-8 (X Fifty Eigt)

 

[cyberbiker]

I had the demo version of VB.net on my laptop as well as VB6 with no problems between the versions.

I did have a problem with Crystal reports VB6 shipped with
Crystal 4.5, I added Crystal 8 but never used the ocx from
VB. VB.Net uses Crystal 8.5.
After I removed the evaluation copy (until I find some extra cash), I later attempted to print a Crystal 8 report from VB and had problems.
Since I never tested any thing directly from VB before this I do not know if the Crystal 8.5 caused the problem or perhaps something else.
Easy fix though. Just browse for the Crystl32.ocx file while in components, click and problem goes away.

I would save off the current Crystl32.ocx control before
installing .net just in case.

Just an aside.

I have installed different versions of the same Microsoft products on the sam PC several times. All I can ever recall doing was placing the newer version in another directory.

Sometimes (as in the case of Access97/Access2000) I get a "Preparing to install" box before the app opens if the last opened was the older app.

But everything works.

It does pay to experiment if you have the time, but be certain to back up everything before you "start messing".




Terry (cyberbiker)

 

[xbafge]

A very wise criterion, LochDhu.

How steep is the learning curve for vb.net? Is VB.Net nothing but VB for .Net or are the differences so many that it amounts to an entirely different ballpark? I mean e.g.:
o is the applications model different
o is the IDE different in nature
o are the standard components such as TextBox etc. different
o does one have to forget Jet and learn MSDE

 

[LochDhu]

The learning curve will be different for each individual, I have 5 years of VB under my belt and I jumped into .NET without much problem. Some things that I have concluded:

If you have never worked with classes in VB your learning curve is greater. Everything in .NET is a class/object. A string variable is an object with properties (.Text for example). ActiveX is gone - well, you can still use ActiveX controls, but you can not create an activeX control). You do get a set of controls with the toolbax (Textbox, Label, etc..) these have *similar* properties and methods that we are used to. VS.NET is completely different but for the better.

My opinion about learning C# is only my opinion because of the developers that I know who have jumped from VB and VC++ to C#. If you look at all the .NET 3rd party controls available:

http://www.infragistics.com

http://www.devexpress.com

http://www.componentone.com

All these controls have been developed with C# - so it's an individual decision on the programmer and his job as to what language may be more advantageous.

Plus, C# developers as whole make more $$ than VB.NET programmers .

If anyone want to experiment with .NET without purchasing VS.NET - here is a link for a free .NET IDE (written in C#).

http://www.icsharpcode.net/OpenSource/SD/

ADO.NET is now available, however I have heard some interesting comments about it. SQL Server is the primary engine (obviously with MS). Oracle has provided a .NET sdk as I am sure other vendors have also.

I hope that helped...

Scott

 

[xbafge]

What this means is that VB.Net will look deceptively like previous versions. Actually ( possibilly excepting the language itself ), every single thing will have to be relearnt - even e.g. the members of TextBox ( who knows the definition of a member may or may not have changed; maybe all the members are not even the same ones ). Right?