OK. I need to build a small app or two and I figure I'll get VB since I created some small nifty apps years ago in VB. So, now it's VB.Net. I figure so what, I'll pick the new nuances up real quick after I install it, no problem. I slip the first CD in and it says it's checking the system for necessary components. I figure I'm OK because I have W2KPro Service Pack 4 Build 2195 with every flippin' update ever put out including the DotNet Framework. WRONG according to the install wizard!

You don't have what you need and you'll have to get it. Let the convoluted process begin. First step -- click here to go to a M$ website and download, DO NOT INSTALL, all service packs and critical and security updates required specifically for VB.Net. Everything is in a list that you have to look at and determine, "Do I have that?". No autoscan and then a pop up list of just what you need. Noooo. Some of the patches listed there go back to the year 2000. How can I NOT have them, I ask you, given that I am up-to-date to the nanosecond?

So ... the instructions say figure out what you need, download the updates to YOUR DESKTOP, DO NOT INSTALL. YOU WILL DO THAT LATER MANUALLY DURING THE VB.NET INSTALLATION.

Next ... disconnect from the internet and any and all other networks. Disable COMPLETELY all AV and firewall software. Have your OS original installation disk ready. Run three or four command line apps. Start the VB.Net and updates installation. Then shutdown, reconnect, reboot, reconfigure, and restart AV and firewall. Bend over, grab ankles, place head firmly between ... You get the picture. You gotta love M$.

Can anyone with VB.Net experience tell me, if I am absolutely up to date, do I need to manually, one by one, check to see if I have updates/patches/etc going back to the birth of Eniac?