FIX: "MS Development Environment has not been installed" error message on Visual Studio .NET 2002 startup (313495)
The information in this article applies to:
- Microsoft Visual Studio .NET (2002), Professional Edition
- Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
- Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
- Microsoft Visual Studio .NET (2002), Academic Edition
This article was previously published under Q313495 IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry
SYMPTOMS When you install Visual Studio .NET and the .NET Framework,
and then you start Visual Studio .NET, you may receive the following error
message: "MS Development Environment has not been
installed for the current user. Please run setup to install the application."
CAUSE This behavior occurs when you try to run Visual Studio .NET
on a computer on which Visual Studio .NET Beta 1 was previously installed.
RESOLUTIONWorkaround To resolve this issue, you must edit the registry on your
computer. WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk. - On the Start menu, click Run, type regedit, and then click OK.
- In the Registry Editor, locate and delete the following
registry key:
HKEY_CLASSES_ROOT\Licenses\C4B8C1BC-A36C-4723-AF48-F362BFAB9DF5
- Close the Registry Editor, and then start Visual Studio
.NET.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
This bug
was corrected in Visual Studio .NET (2003).
Modification Type: | Minor | Last Reviewed: | 1/19/2006 |
---|
Keywords: | kbtshoot kbvs2005doesnotapply kbvs2005swept kbvs2002sp1sweep kbfix kbbug kbnofix KB313495 kbAudDeveloper |
---|
|