Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Visual Studio 2005 previous beta removal tool

Visual Studio 2005 previous beta removal tool

  • Comments 42

Hey all, I'm sorry for the delay posting this.  I've got a version of the cleanup tool that I wrote that I specifically tailored to automate that long list of removal steps listed here and here.

You can download and try out the VS 2005 beta removal tool by going to this link.

Note that this tool isn't "officially" supported by Microsoft or me.  That being said, please let me know if you have any trouble getting this to work on your computers.  My next step is to create a version of this tool that will automate all of the manual removal steps for the .NET Framework 2.0.  Stay tuned....

As a side note, I was hoping to have it ready when VS 2005 and .NET Framework 2.0 beta 2 went live on Sunday, but obviously that didn't happen.  I apologize to the folks who have contacted me with broken machines and wasted days cleaning them up (and also those who have gotten burned by the manual uninstall but haven't contacted me).  I know it is not really any consolation now, but we're really working hard to do what we can to fix any broken machines without forcing you to reformat and also to get any of the underlying setup bugs fixed by the time VS 2005 ships.  Thank you for your patience and interest in VS 2005 and .NET Framework 2.0.

 

  • Hi there - ran the tool, and re-installed beta 2, but Im still getting the following messages when creating a project and switching to the designer:

    Package 'Visual Studio Settings and Project Designers Package' has failed to load properly ( GUID = {67909B06-91E9-4F3E-AB50-495046BE9A9A} ). Please contact package vendor for assistance. Application restart is recommended, due to possible environment corruption. Would you like to disable loading this package in the future? You may use 'devenv /resetskippkgs' to re-enable package loading.

    and

    Could not load type 'Microsoft.VisualStudio.Shell.Interop.IVsRunningDocumentTable2' from assembly 'Microsoft.VisualStudio.Shell.Interop.8.0, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
  • I'm also still getting the error, when trying to open the form designer and other errors while trying to open diffrent designer (e.g. Dataset designer). I have completely uninstalled Beta1 first manually as suggested, then ran the tool.

    Just to note I have already spended 3 days playing around with this problem, I hope that you folks could come up with something to fix this.

    ---------------------------
    Microsoft Visual Studio
    ---------------------------
    Could not load type 'Microsoft.VisualStudio.Shell.Interop.IVsRunningDocumentTable2' from assembly 'Microsoft.VisualStudio.Shell.Interop.8.0, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
    ---------------------------
    OK
    ---------------------------
  • Hi, just to make sure. If i run this tool, would it remove all the beta 1 bits that i've installed in my machine? Thanks.
  • I wanted to clarify a couple of things here. This tool is intended to automate the manual cleanup steps on the VS 2005 download page. So if you intend to use the tool you should not try to uninstall each of the packages beforehand unless you follow the exact order listed on the uninstall page.

    Also, if you are seeing IDE crashes or package load failure errors after installing beta 2 and launching the IDE, please try to use the workaround listed in the "IDE may fail to launch" section of this blog post - http://blogs.msdn.com/astebner/archive/2005/04/16/408860.aspx

    I am working on a way to automate those workarounds as part of the cleanup tool but have not had time yet :-(
  • I got a chance to investigate a couple of machines from Microsoft employees who ran into issues after...
  • Following and acting on this thread has helped but I am still experiencing problems with Beta 2 setup.

    Your removal tool got rid of the package load problems but I am still getting Dr Watsons during the initial setup process which looking at the error log seems to suggest the setup process is getting confused:

    [04/24/05,11:13:31] .NET Compact Framework 2.0: [2] Error code 1618 for this component means "Another installation is already in progress. Complete that installation before proceeding with this install.
    "
    [04/24/05,11:13:31] .NET Compact Framework 2.0: [2] Setup Failed on component .NET Compact Framework 2.0
    [04/24/05,11:15:52] Microsoft SQL Server 2005 Express Edition April CTP: [2] Error code 1603 for this component means "Fatal error during installation.
    "
    [04/24/05,11:15:54] Microsoft SQL Server 2005 Express Edition April CTP: [2] Setup Failed on component Microsoft SQL Server 2005 Express Edition April CTP
    [04/24/05,11:16:09] Microsoft Device Emulator version 1.0 Beta 2: [2] Error code 1618 for this component means "Another installation is already in progress. Complete that installation before proceeding with this install.
    "
    [04/24/05,11:16:10] Microsoft Device Emulator version 1.0 Beta 2: [2] Setup Failed on component Microsoft Device Emulator version 1.0 Beta 2
    ***EndOfSession***

    I have tried several de-install re-install cycles with reboots between them without being able to get past these errors.

    However I am manually able to execute the above failed files and get everything installed apparently correctly. Indeed everything seems to work apart from when trying to connect to a PPC device emulator. I am getting the "VPC network driver" error that you described in a previous blog in connection with Beta 1. The solution you proposed for Beta 1 does not work with me for Beta 2.

    Thanks,

    JJ
  • I tried to do this manually, but then saw your posting. It seems to work. Thank You very much, and shame on you Bill, you should not send things like this from Redmond.
  • this is a very useful tool - i had the same problem - i wonder why nobody tested this scenario. thanks for the cooking up the tool.
  • Great Tool
    Thanks from Switzerland
    Heidi
  • Thanks, this works!! good tool!!
  • Thanks for this Aaron - worked perfectly.
    It really should have a higher profile - should be on the MSDN website or the distribution CD or something!

    pg
Page 1 of 3 (42 items) 123
Leave a Comment
  • Please add 8 and 8 and type the answer here:
  • Post