Microsoft .NET Framework Repair and Uninstall/Reinstall Procedures

Background

Wasp software products rely on the Microsoft .NET Framework for many operations. Corruption in .NET can cause Wasp products to fail or give errors with no apparent Wasp-related cause. For example, a problem persists even after deleting and reinstalling all components of a Wasp software product.

When .NET version numbers show up in error messages, log files, and Windows Event Viewer, this is evidence of .NET problems. These version numbers can be seen as subfolder names under C:\Windows\Microsoft.NET\, including v1.0.3705, v1.1.4322, v2.0.50727, v3.0, v3.5, v4.0.30319.

Error keywords & files that point to .NET problems:

mscorlib

mscorlib.dll

KERNELBASE.dll

An example from a Windows Application Event Log follows. Note that the version number matches .NET, not the installed Wasp component (which is v7.3).