Jeremy D. Miller -- The Shade Tree Developer

Sponsors

The Lounge

Wicked Cool Jobs

Syndication

News

Advertisement

Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
The only thing I miss from VB6

There was some VB6 abuse from me & other commenters yesterday.  I gotta say that I do miss one thing (maybe two):

  1. Intellisense for enumerations was better in VB6 than VS & C#
  2. With/End With - sorta
I can't think of anything good to say about COM/COM+/DCOM.  They can stay dead to me. 

Posted Tue, Mar 27 2007 11:56 AM by Jeremy D. Miller

[Advertisement]

Comments

mgroves wrote re: The only thing I miss from VB6
on Tue, Mar 27 2007 12:40 PM

Oh lord, the With blocks.  DO NOT WANT.

Console.Write(this.Opinion) wrote Saudades do VB6... será?
on Tue, Mar 27 2007 1:15 PM

Não sou o único com saudades do With/End do Visual Basic, lembram dele? Ficava legível e mais rápido.

Chris Brandsma wrote re: The only thing I miss from VB6
on Tue, Mar 27 2007 3:16 PM

Boy, I'm going to loose my coder status with this one...

I am also no lover of COM/ActiveX, but DANG there is a lot of software still out there using it.  And VB is still one of the fastest ways to slap together a quick and dirty DLL.  So I will admit to doing a few (little) integration pieces in VB6.  

Bonus: my manager was happy that we didn't have to muck with any of that .NET deployment mess.  (sorry, many/most machines still don't have .NET installed)

Only problem is that I needed a shower as soon as it was done.

Harris wrote re: The only thing I miss from VB6
on Thu, Mar 29 2007 8:19 AM

Man, it's been so long since I've messed with VB6 I don't even remember what could be special about enumerations...

To me, the With block isn't anything spectacular and it seems almost like a code-smell...I mean, essentially it's method chaining, but without restricting you to methods since you can set property values.  So, if you wanted to do it in C#, you'd have to resort to Java-style coding for setting properties and then returning this every time.  Nevermind the fact that you are then communicating that the object is immutable (think NHibernate's Configuration object) when, if it were an entity, that's most-likely not the case.

I dunno.  Maybe that's making a mountain out of a mole-hill...

Add a Comment

(required)  
(optional)
(required)  
Remember Me?
Devlicio.us