VB6 or VB.Net 1

[CPUCurt]

I’m looking for solid references, both Pro and Con, for moving to VB.NET.

Any help or testimonials would be appreciated.

 

[BobRodes]

This is a good book.

http://www.amazon.com/exec/obidos/t...ne/purchase/ref=pd_sxp_r0/002-8918882-5510413

 

[VBakias]

No doubt -> VB.NET
-Pros are too many
-Cons: i'll tell one, .NET framework must be installed to the pcs so the application works. But you may add to the app of yours a setup project (to instal what is needed, reg entries, etc)


-

 

[toon10]

VB 6 is full of bugs you have to find by accident and then fix, .NET seems more stable.

 

[LazyMe]

VB 6 is full of bugs you have to find by accident and then fix, .NET seems more stable.

Or just isn't as widely used as VB6 yet and therefore just seems more stable.

Being said that; can you present your list of bugs you have to fix in VB? Since it's so full it must be quite a list?

Greetings,
Rick

 

[bjd4jc]

I second the request for the "list full of bugs"

I guess I, haven't run into them... that is if we have the same definition of a bug...

 

[strongm]

I'm looking forward to the list as well ...

 

[chiph]

Yup, while there are some things in VB6 that a programmer just shouldn't do, I haven't really run into a flat-out bug in it.

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first

 

[BobRodes]

Well, I found one in the DataRepeater control. Also, that book I mentioned makes some very good points about when and when not to use .Net.

Bob

 

[LazyMe]

In the datarepeater control?

Never used that, but since that's just an activex control and not part of VB I wouldn't call that a VB bug; it would just as well arise when using the control from within C++, for example, wouldn't it?

Greetings,
Rick

 

[strongm]

Given that the DataRepeater is a bundled ActiveX control that wasn't even included in all releases of VB6, I reckon it is stretching it a bit to suggest that a bug in it represents a bug in VB ...

 

[strongm]

Ah - you beat me to it!

 

[BobRodes]

Yes, any of the bugs I can remember encountering using VB have to do with dlls or controls.

Mea culpa...

Bob

 

[DrJavaJoe]

We don't take kindly to folks talkin badly about our programmin language round here.


Two strings walk into a bar. The first string says to the bartender: 'Bartender, I'll have a beer. u.5n$x5t?*&4ru!2[sACC~ErJ'. The second string says: 'Pardon my friend, he isn't NULL terminated'.

 

[strongm]

Heh!

 

[DrJavaJoe]

You don't speak Texan? I thought it was funny how quickly everyone came to defend Visual Basic after toon10's post.


Two strings walk into a bar. The first string says to the bartender: 'Bartender, I'll have a beer. u.5n$x5t?*&4ru!2[sACC~ErJ'. The second string says: 'Pardon my friend, he isn't NULL terminated'.

 

[BobRodes]

Oh, now, come on! I love VB, warts and all.

 

[BobRodes]

Furthermore, as I have often said, the vagaries of VB simply allow us to charge more money for our time.

 

[toon10]

Here's the last one I had to work around...

http://support.microsoft.com/default.aspx?scid=kb;en-us;216666

 

[strongm]

But that's not a bug. It is how the DataEnvironment is designed to work (as the KB article points out). Sure, we can argue about whether it is a smart design decision, but that still does not make it a bug.

Next ...