Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
Now that the .NET Framework 2.0 and VS 2005 are officially released, those of you who have been running beta and CTP builds will need to prepare your machines to install the final release. As I'm sure many of you are aware of if you've had a beta installed in the past, beta uninstall and migration to newer builds has been a very painful subject dating all the way back to VS 2005 and .NET Framework 2.0 beta 1. Fortunately there is a lot more awareness that uninstalling the various pieces of VS 2005 is not trivial, and there are some automated uninstall tools and much better documentation.
For those of you who will need to uninstall a previous beta in order to install the final release of VS 2005 and/or the .NET Framework 2.0, you should make sure to review the official uninstall instructions before starting to uninstall anything. In case you read nothing else, please make sure that you leave the .NET Framework 2.0 beta uninstall until the very end. Most of the other pieces of VS 2005 will not uninstall fully if you remove the .NET Framework 2.0 beta first, and that can cause problems in some scenarios after installing the final release.
In order to make the uninstall process easier, there are a couple of automated uninstall tools available for various scenarios:
The uninstall tools (#1, #3 and #4 above) are designed to run Windows Installer APIs and command lines to discover whether or not a known, fixed set of products are installed and then remove them. As we discover additional issues that these tools do not cover, I will be updating the troubleshooting tool. The main goal of the troubleshooting tool is to fix up a machine that already has the final release installed without needing to have the user resort to uninstalling everything and starting from scratch. It tries to perform more "surgical" fixes for specific issues related to incomplete/incorrect beta uninstalls.
As always, let me know if you run into any issues or have any feedback on any of the above tools and I'll try my best to help.
Where to get Visual Studio 2005 and the .NET Framework 2.0 Where to download the .NET Framework 2.0 redistributable
Hi Aaron -- I have struggled for two days to get VB Express 2005 final release running, but no luck. Trouble started after I installed VB 2008 beta, VWD express and SQL Server express. Before that it ran great for months.
I am currently in the mode where I get six package load failures on startup. This is after I have run the "Hammer" and re-installed from CD (burned from downloaded iso image).
The only thing I have not tried is to run the troubleshooting tool (Ttool.zip) because the link appears to be broken. Is there another place to get it? Is there anything else I should be trying?
Hi ZookManPat - If you had any previous beta versions of Visual Studio 2005 installed on your system, I'd suggest trying the steps listed at http://blogs.msdn.com/astebner/archive/2005/12/16/504906.aspx. My file server is currently down for maintenance, but it should be back up soon so you can check back in a day or so and hopefully it will be available for download again. I'm sorry for the hassle that this issue is causing for you.
If this problem started after installing the VS 2008 beta, I'd also suggest reporting a bug on the bug reporting site at http://connect.microsoft.com/visualstudio/.
Thanks for the timely reply, Aaron. I went through the steps at 504906, except for #2. Any chance you could email me the troubleshooting tool so I could try that? My email is patwiegand at suddenlink dot net.
I post on this with every release, but I'll post something about the latest blog entry on it. The
PingBack from http://www.pc-helpforum.be/f167/just-time-debugging-error-7767/#post33681