I am trying the below right now.
Copied from: http://blogs.msdn.com/astebner/archive/2005/11/10/491653.aspx
The underlying problem was that VS setup detected that the .NET Framework 2.0 was already installed and skipped that prerequisite step. However, the machine did not actually have the .NET Framework 2.0 installed, but instead only had the registry key that VS setup uses to detect whether or not the .NET Framework 2.0 is installed. I found that the machines had the following orphaned registry key/value that VS setup uses to determine that .NET Framework 2.0 was already installed:
- Key name: HKLM\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727
- Value name: MSI
- Data type: REG_DWORD
- Value data: 1
Once the customers deleted this key/value and re-ran VS 2005 setup, it detected that it needed to install the .NET Framework 2.0, and after installing that, VS setup worked perfectly.
|