Updating VS.NET

by Erik Lane 1. February 2006 05:59

When updating Microsoft Software be sure to use the same version AND source as the original install.

Last night I was "forced" to install VB.NET to go through some sample code I had.  I've been able to translate smaller pieces to C# but this was a full project that I wanted to make some changes to and get it to compile and work on its own.  This isn't going to be a VB.NET  vs. C# post I promise.

Why can I not update a piece of software as long as its the same brand/version/etc..?  All I wanted to do was update my current installation.  I had the CD's on-hand so no problem right?  It would've been if I had remembered that I had installed the Enterprise Architect version and not Professional; which is the set I had on-hand.  So off to subscriber downloads I go to get the correct version.  No issue here, I understand the need for the correct version.

After downloading and burning the images I'm ready to roll?  Negative ghost rider.  This time it was expecting the DVD version since I had installed it using the DVD's in the office.  It even told me I could browse to the MSI package if the original source wasn't available.  I did what they suggested and still no dice.

At this point I'm remembering back when I had something similar happen with MS Office where I just ended up uninstalling and reinstalling the whole thing.  Office is a quicker install than VS.NET so I wanted to avoid that whole scene.  Next step was to download the full install version and pray that it doesn't need to be burned to a DVD as I don't have a DVD burner readily available.  That was the ticket!  Turns out that I didn't have to burn it to DVD and it let me use the MSI package that I pointed it to.

To recap for those not following along:  When updating Microsoft Software be sure to use the same version AND source as the original install.

Tags:
Comments are closed