Thursday, May 13, 2010

Two Terrific Troubleshooting Tools -The .NET Framework Cleanup and Setup Verification Tools

Aaron Stebner's WebLog - Updated versions of .NET Framework cleanup and verification tools that work with the .NET Framework 4

“Over the past week or so, I finally found some time to update the .NET Framework cleanup and verification tools to support the recently released .NET Framework 4 product family.  I have uploaded new versions of both tools, and you can find more information about the tools and download links in their users guides.  Here are links for the users guides for each of these tools:

…”

Aaron Stebner's WebLog - .NET Framework Cleanup Tool User's Guide

Introduction

This .NET Framework cleanup tool is designed to automatically perform a set of steps to remove selected versions of the .NET Framework from a computer.  It will remove files, directories, registry keys and values and Windows Installer product registration information for the .NET Framework.  The tool is intended primarily to return your system to a known (relatively clean) state in case you are encountering .NET Framework installation, uninstallation, repair or patching errors so that you can try to install again.

There are a couple of very important caveats that you should review before using this tool to remove any version of the .NET Framework from your system:

  • This tool is designed as a last resort for cases where install, uninstall, repair or patch installation did not succeed for unusual reasons.  It is not a substitute for the standard uninstall procedure.  You should try the steps listed in this blog post before using this cleanup tool.
  • This cleanup tool will delete shared files and registry keys used by other versions of the .NET Framework.  If you run the cleanup tool, you will need to perform a repair/re-install for all other versions of the .NET Framework that are on your computer or they will not work correctly afterwards.

Supported products

The .NET Framework cleanup tool supports removing the following products:

  • .NET Framework - All Versions
  • .NET Framework - All Versions (Tablet PC and Media Center)
  • .NET Framework - All Versions (Windows Server 2003)
  • .NET Framework - All Versions (Windows Vista and Windows Server 2008)
  • .NET Framework 1.0
  • .NET Framework 1.1
  • .NET Framework 2.0
  • .NET Framework 3.0
  • .NET Framework 3.5
  • .NET Framework 4

image …”

Aaron Stebner's WebLog - .NET Framework Setup Verification Tool User's Guide

Introduction

This .NET Framework setup verification tool is designed to automatically perform a set of steps to verify the installation state of one or more versions of the .NET Framework on a computer.  It will verify the presence of files, directories, registry keys and values for the .NET Framework.  It will also verify that simple applications that use the .NET Framework can be run correctly.

Supported products

The .NET Framework setup verification tool supports removing the following products:

  • .NET Framework 1.0
  • .NET Framework 1.1
  • .NET Framework 1.1 SP1
  • .NET Framework 2.0
  • .NET Framework 2.0 SP1
  • .NET Framework 2.0 SP2
  • .NET Framework 3.0
  • .NET Framework 3.0 SP1
  • .NET Framework 3.0 SP2
  • .NET Framework 3.5
  • .NET Framework 3.5 SP1
  • .NET Framework 4 Client
  • .NET Framework 4 Full

By default, the .NET Framework setup verification tool will only list versions of the .NET Framework that it detects are installed on the computer that it is being run on.  As a result, the tool will not list all of the above versions of the .NET Framework.  This product filtering can be overridden by running the .NET Framework setup verification tool with the following command line switch:

image …”

A couple tools here that I didn’t know about but I could see saving a ton of time isolating, troubleshooting and resolving .Net installation issues…

 

Blog Note: Based on some feedback, I’m going to try some minor changes to the thumbnails/page preview images I sometimes provide (like those above). Where an image is meant to be an overview/preview/get a feel of the content that I’m referencing/etc shots, instead of “medium” I’m going to go with “small” images (i.e. more thumbnail like). This will hopefully still provide you a feel for what I’m referencing/quoting/curating and help you make the call if you want to travel further down the path, while limiting “visual noise”. Worth a try at least (and smaller images will mean for faster downloads too, so there’s that! :)

No comments: