MBR IT/.NET 247 : MS Development Environment has not been installed for the current on microsoft.public.vsnet.setup

MS Development Environment has not been installed for the current

Messages

Related Types

This message was discovered on microsoft.public.vsnet.setup.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.

Post a new message to this list...

Denver Developer (VIP)

I am suddenly receiving this message when I try to start VS 2003. KB article
302586 indicates this is associated with VS .Net only. (VS.Net will start
fine)

The only recent change I made was a change to the registry to trap device
drivers that do not complete based on instructions from a MS feedback from
submitting an error report for a system failure.

I have NOT yet loaded VS 2005.

I have tried to re-install but that does not help

Reply to this message...

CambsDev (VIP)

This is not going to be of any help to you, as I am having the same problems
but wanted to add my voice to your post to let you know you are not the only
one with this problem.

I am currently experiencing the same problem. Whenever I try to load Visual
Studio .Net 2003 (Enterprise Architect), MSDN Universal licence, I am
prompted to insert the installation disk, if I cancel the dialog I get the
message "MS Development Environment has not been installed for the current
user...". If I insert the installation disk the system starts properly but
when I try to load VS at the start of each day I get the same problem.

This problem is shared by another colleague. Neither of us have the registry
key (kb 313495):

HKEY_CLASSES_ROOT\Licenses\C4B8C1BC-A36C-4723-AF48-F362BFAB9DF5

We both have .NET framework version 1.1 service pack 1 and MSDN (July 2004)
installed. Neither of us have any .NET betas installed.

I have tried manually repairing the install but the problem still occurs
when I next load up the software. I have also tried tracking the License
registry keys that VS tries to access during startup. If I delete certain
keys I do not get as far (ths sytem just refuses to start) and other keys
have no visible effect if I delete them.

I have tried backing up, then deleting the keys VS tries to access under
HKEY_CLASSES_ROOT\Licenses before running a repair install and still no luck.

"Denver Developer" wrote:

[Original message clipped]

Reply to this message...

MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

	Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
	Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com