Something is caught in the .Net I think

A discussion with a colleague about a software problem relating to Sage Accounts (a UK accounting package) and .Net lead to an interesting find. Despite repeated attempts to remove .Net to facilitate fixing the underlying Sage problem he could not get it to remove itself correctly

The tool that did work can be found here and the author Aaron Stebner posted an updated version of the .NET Framework cleanup tool that now contains support for automatically cleaning up the .NET Framework 1.0, the .NET Framework 1.1, the .NET Framework 2.0, the .NET Framework 3.0 and the .NET Framework 3.5.