Jay Glynn's Blog

I'd rather be coding

  Home  |   Contact  |   Syndication    |   Login
  66 Posts | 0 Stories | 4 Comments | 62 Trackbacks

News

Archives

Post Categories

Image Galleries

OK, so I figuered out why I lost my changes, in VS the default is to save before running, in VB 6 the default is don't save. I can take the blame for that I guess, but why wouldn't the default be to save the work before running or compiling? To make matters worse, I'm in the middle of making the changes again, and the power in the building goes out. Now this time I had been saving more often, and set the save before running option, but I have about 45 minutes worth that I'll have to do **AGAIN** for the third time.

Now the losing of work may be partially my fault, VB is the one that decided to crash after all, but I really do have to say that writing VB 6 after spending the last several years in .NET is painful. I keep running into little things that I can't do that can be done with ease in .NET. Along with the ones I mentioned before, inheritence and proper exception handling come to mind. Not being able to do reflection (I didn't know how much I used this) is another one.

I think I'm going to get some lunch before I start this again....

posted on Friday, April 23, 2004 1:48 PM