 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / New Users / December 2004Executing VS.NET ERROR: Ms development environment has not been installed for the current user
Can get VS.Net to execute properly. I'm not the only one having this prob. The registry deletions don't work for me. Any users of MVPs have a solution for this? This error appears to have re-emerged. The KB article that describes the registry changes was for people who installed the .NET beta, which is clearly not applicable. Help me to figure out how to reproduce this error and perhaps we can solve this, or at least provide info to someone at MS who can jump in. First off: what versions of the framework do you have installed? When did you install VS.NET? What version? What version of the OS did you have installed on the day you installed VS.NET? Have you upgraded? Did VS.NET work for some time before it stopped working? How long did it work? How long has it not worked? If you are running XP SP2, please provide the order in which you installed software: framework, sp2, visual studio Are you running the Visual Studio 2005 beta? If so, what version? Are you running virus scanning software? If so, what package and version? Were they running when you installed vs.net or SP2? --- Nick > Can get VS.Net to execute properly. > I'm not the only one having this prob. > > The registry deletions don't work for me. > > Any users of MVPs have a solution for this? Thanks for the quick reply Nick, My answers in line... > This error appears to have re-emerged. The KB article that describes the > registry changes was for people who installed the .NET beta, which is [quoted text clipped - 4 lines] > > First off: what versions of the framework do you have installed? 1.1 2 beta > When did you install VS.NET? December 7 2004 What version? 2003 Academic > What version of the OS did you have installed on the day you installed > VS.NET? XP SP2 > Have you upgraded? No > Did VS.NET work for some time before it stopped working? No > How long did it work? Never How long has it not worked? Since install > If you are running XP SP2, please provide the order in which you installed > software: framework, sp2, visual studio Followed install procedures from vs.net academic 2003 > Are you running the Visual Studio 2005 beta? No If so, what version? > Are you running virus scanning software? No If so, what package and version? > Were they running when you installed vs.net or SP2? No > --- Nick > [quoted text clipped - 4 lines] >> >> Any users of MVPs have a solution for this? The one thing that stands out is that you have framework 2.0 beta paired with Visual Studio Academic. Did you install the framework 2.0 before installing Visual Studio Academic or after? --- Nick > Thanks for the quick reply Nick, > My answers in line... [quoted text clipped - 44 lines] > >> > >> Any users of MVPs have a solution for this? before - and don't know where it came from as the computer is only two weeks old. Now I'm getting all kinds of problems trying to uninstall... > The one thing that stands out is that you have framework 2.0 beta paired > with Visual Studio Academic. [quoted text clipped - 55 lines] >> >> >> >> Any users of MVPs have a solution for this? From Fred Morison in another post found here Take a look at KB article 824643. It essentially has you manually deinstall Framework 1.1, then reinstall Framework 1.1 followed by install of Framework 1.1 Sp1, all while running in a "clean boot + Windows Installer service only" mode. Some of the "uninstall" parts didn't work for me, but manually deleting the various .Net Framework related .msi files from C:\<windir>\Installer\ as directed by KB 824643 worked just as well. Kind of stupid of Microsoft to make us do it this way (deinstall everything, reinstall everything), but it worked for me after weeks of frustration. This cleared the Framework 1.1. uninstall problems.... > before - and don't know where it came from as the computer is only two > weeks old. [quoted text clipped - 61 lines] >>> >> >>> >> Any users of MVPs have a solution for this? but still can't get .net to uninstall.... > From Fred Morison in another post found here > [quoted text clipped - 80 lines] >>>> >> >>>> >> Any users of MVPs have a solution for this? Couldn't get vs.net 2003 Academic version to uninstall so I thought I would try to install it and if it still errored out then try uninstalling it again. So I installed it properly again - successfully asked for serial number etc... Tried to run abain and DID NOT get this error when executing vs.net. It allowed me to register online and looks to be working properly. -------------------- So what did I do? Uninstalled framework 2 beta. Uninstalled framework 1.1 using KB article 824643 And reinstalled vs.net 2003 Academic All looks well now.... Waisted 2 full days of study on this. > but still can't get .net to uninstall.... > [quoted text clipped - 85 lines] >>>>> >> >>>>> >> Any users of MVPs have a solution for this? You are the first person I've seen who got this to work. Congrats! --- Nick > Couldn't get vs.net 2003 Academic version to uninstall so I thought I would > try to install it and if it still errored out then try uninstalling it [quoted text clipped - 107 lines] > >>>>> >> > >>>>> >> Any users of MVPs have a solution for this? > before - and don't know where it came from as the computer is only two weeks > old. > > Now I'm getting all kinds of problems trying to uninstall... Sorry to intrude, but I have to ask: does anybody else have access to that PC? The .NET Framework v2 beta had to have been installed by someone or something. I suspect that your problems were related to the existence of the beta software. I'm glad you were able to resolve the problem, and thank you for posting your solution.  SignaturePeter [MVP Visual Developer] Jack of all trades, master of none. Hi Peter, Thanks for the reply. I try to post my solutions but would prefer to be able to retrieve them 6 months from now. The install file for the v2 beta had either the same name as v1.1 or a very non-discript name. So I could have installed it by mistake when trying to install v1.1. Or could have at the time of installtion of v2 beta made an informed decision to go ahead and try v2 beta. >> before - and don't know where it came from as the computer is only two > weeks [quoted text clipped - 9 lines] > I'm glad you were able to resolve the problem, and thank you for posting > your solution. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.