Re: VB6 vs VB.NET

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Bob Butler (tiredofit_at_nospam.com)
Date: 09/09/04 

Date: Thu, 9 Sep 2004 06:33:12 -0700

"Patty O'Dors" <Patty O'Dors@discussions.microsoft.com> wrote in
message news:240F961F-0623-41B5-B7E8-986A0125CA77@microsoft.com
> * It uses Legacy VB6 functions like CStr rather than the object-
> orientated methods like ToString()

Surely that's the programmer's choice; you can restrict yourself to a more
austere VB.Net if you don't want to use the VB6-style functions

> * It can't do like operator overloadning, like "public static explicit
> operator string" - which is my main gripe.

Isn't that added in VB.Net 2005

> * There's reports out there suggesting that Vb.NET falls over when
> dealing with large projects - see
> http://blogs.msdn.com/csharpfaq/archive/2004/03/11/87816.aspx
> * unsigned data types - C# has them, VB.NET doesn't

Isn't that added in VB.Net 2005

> I could go on, but I've got work to do.

That I find hard to believe and somehow terrifying at the same time 

-- 
Reply to the group so all can participate
VB.Net... just say "No"