GHOST restores Win2003, DOTNET has been this problem, and there is a blog explained as follows:
This is generally the reason for the two-system, and Windows Installer discovers that TLBs and DLLs already exist. It is no longer registered, and can be repaired in 2 in the control panel, you can select 2 MS. Support Q320427.
Checked MSDN because of the dual system, but due to multiple installations, TLBs, DLLs existed, my dual system is Win2003, SUSE Linux,
Quote Q320427 as follows:
PRB: "VC Package Not Available or Not Registered" Error Message
Suitable
This Article Was previously Published Under Q320427
Symptoms
WHEN You Create a Winforms Application, You May Receive The Following Error Message:
"Vc package not available or not register"
. En o o o.
Cause
This behavior seems to occur because the Windows Installer does not register TLBs and DLLs if the installer finds that these items already exist. In most cases, a previous version of Visual Studio .NET causes this behavior, even if the previous installation was under a different Operating system.
Resolution
.. To resolve the problem, run the Visual Studio .NET repair A repair is more effective for fixing this issue because the repair process forces registration of items that are not re-registered during an install To run the repair, follow these steps:
On the Start menu, point to Settings, click Control Panel, and then click Add / Remove Programs. On the list of installed programs, click Visual Studio .NET, and then click Change. Click the second item in the 1 2 3 Visual Studio Setup Dialog Box. Click Repair / Re-Install, And The Follow The OnScreen Instructions.
More information
Steps to reproduce the behavior
To reproduce the problem, it is best to have two operating systems installed on separate partitions Two installations of Windows XP Professional will work.Install Visual Studio .NET under one operating system Install Visual Studio .NET under the other operating system;.. Change the DEFAULT LOCATION TO MATCH The Installation Location of The First Installation. Both Installs Report As Successful. Start The Copy Of Visual Studio .Net That You Installed in Step 2.
This type of installation is never recommended. Even if the installation selections are exactly the same, and you can save disk space by performing this type of installation, the potential for problems is high. If one installation changes files and registry entries, these changes are NOT Recorded by The Other Installation, Which Creates A Substantial Risk for UNEXPECTED RESULTS.
