Visual Basic .NET Nightmare or Guide to upgrading a Guru.

Part Deux

Page 2

Should I Uninstall before I install?


Q1. Do you have distributed apps built on 2002?

 A. You may wish to keep 2002 around to do quick bug fixes or supplemental additions to your code without killing your client with a full upgrade.

 Q2. Are you willing to migrate your 2002 projects to 2003?

 A. This may be harder than it first appears. I would never dream of changing a VB 6 App to Dot Net, but supposedly the wizard can do this. Will processes fail under 2003 that worked under 2002? It’s possible.

 Consider the curve. Okay, this may be hard to follow so I’ll be complete here as I can. The earliest versions of VB were short lived.  The same thing is happening with Dot Net versions. Since it’s so new it’s rapidly being altered to work better. I can’t even tell you anything about VB 1 or 2.  I never saw them, they came and went while I was messing around with machine code on the old green screen. I got VB 4.0 for win 95. The whole 16 bit to 32 bit thing might have been a nightmare back then, but I wasn’t privy to it. I did use VB 3.0 a bit on campus, the same place I taught the very competent Programming/Computer teacher both Win 95 and Office 95. Yes he was supposed to be teaching us!  Anyway I digress.  4.0 was stable much longer, VB 5.0 (Did anyone buy this?) to me was a free Control Creation Edition that would not compile into exes. 4.0 lived on until 6.0, which still holds its weight on the market today as viable, especially if you had the whole studio, which I do.

 So VB Net 2002, and 2003 are comparable to VB 2, 3. Following?

 Q3. Should I uninstall before I install?

 A. if you answered Yes to Q1 and No Q2 then no. Otherwise be like me and go out with the old and in with the new. 

 Just an FYI: I have yet to put the DNF 1.1 in my computer. So I’ll be doing that, too.


 I believe 2003 wants office 2003 installed. I had the Office 2003 Beta installed and uninstalled it. Since then my VB 7 IDE has been unable to start a new project.

 See my error.


 If you have Office 2003, which I don’t, I would definitely want it installed first. When I do finally purchase that gigantic software I may be forced to do some uninstalling and reinstalling then.

 So, I am uninstalling VB Dot Net 2002 (They should have called it the learning edition, did anyone accidentally buy VB 6.0 Learning edition and have a cow as a results like I did?)

 Step one: Turn all unnecessary programs off. Including your anti everything software. If you’ve been surfing the web and listening to MP3s and writing in word, like I have, a fresh reboot might be good with everything in auto start turned off.

 How to: Click run, type in MSconfig and go to the start up tab, uncheck everything that you know will not cause the system not to work. If you’re like me, you may not have any sound when you do this, but windows should run without all of this stuff.  Remember this guide is for gurus, if you don’t know what your doing here, don’t do it – That’s my disclaimer for everything before and that follows!

Step Two: Uninstall VB Net 2002. No Problem.

Step Three: Uninstall DNF 1.0. This is optional. For me I see no reason to keep this at this time. If for any reason a program I already have installed, by some other vendor, requires it, I’m sure I’ll be notified. If no alerts should ever come up, I’ll not be surprised. No problem.

Step Four: Reboot again, clear that RAM.  Get your VB CD ready.

Step Five: Install VB 2003. The first thing to note is the lack of disks compared to 2002.  What we have is a service Pack 4 disk for 2K, nice addition.   A perquisites disk as apposed to a component update disk. 3 disks of the MSDN Library and One, yes I only see one setup disk. Who wants to bet me the moment I get it started it’s going to ask for the perquisites disk? Good thing I’m finally a two CDRom computer user!

 Yes, you have to put in the appropriate drive letter. This MS software is so fancy!

 Ah, what a surprise, it wants to install DNF 1.1, first.  Does this come with the service pack or not? Nope, there it be on Windows update waiting for the windows user to have it automatically downloaded and installed without their knowing. But hey, that’s easier for us, right? Right? Right?

 Good news is installing DNF 1.1 auto reboots. Cool, because I was away when it did that. Time saved!

Q4. So should I get service pack for DNF 1.1 next?

 A. Randy’s rule of thumb is thus. Install in order to numbers. Since SP1 for DNF 1.1 did not come on the disk, I would not update it at this time. The setup code was programmed on 1.1 only. Now, there may be absolutely no problem getting the SP first, but why risk it and waste time? So no, you can install SP DNF after you get VB Installed.

 So go ahead and install VB Net 2003 as per step 2 on the install screen.

 Tip 1: Don’t look at the screen when typing in the CDKey, the dashes are not in line with the separate text boxes on the screen.

 Is this not fat? At 742 MB required for install, I can’t be that far off about the 1 gig program, can I? Yes this doesn’t include games with numerous files for graphics, they have gone beyond a gig, but a straight up program. We be close!

 Step Six: Watch a movie while you wait. Personally I was in the mood for HP 3 for a second viewing.

Install complete, success, no errors. Just to recap, I have Windows XP Pro w/SP1, Office XP Pro. My hardware is two years old, but plenty for this adventure. Let’s check this puppy out!


Page 3