Last post Sep 25, 2015 06:55 AM by PatriceSc
May 21, 2009 10:56 AM|rvegab00|LINK
I am upgrading our visual studio installation for student lab computers from visual studio 2005 to visual studio 2008.
These computers are in a frozen state, such that each time they are rebooted they remove all changes done but the user and "refresh" to the preset system load created by me.
The "visual studio is preparing to start for the first time" message has plauged us in the 2005 version of visual studio and looks to also be a problem in 2008. I had read some articles about how to stop this message from appear and found the following
Click on the Tools > Options... Select "Import and Export Settings", and change the path under "Automatically save my settings to this file:" to a path that is NOT under the "My Documents" directory
Since we have the students my documents pointed to network storage, i figured the suggestion would work.
However, when I tried to do this, and set the file path to the root of the c drive, but then when visual studio is started it throws an error saying it can not find the file? I'll have to pull up the extact error I appoligize.
This message is a real pain in the ass and some of the professors are getting a bit irrate about it, which I can understand.
Thoughts suggestions? - I will provide the error message that is gives when I changed the path to the root of the c drive.
Jun 05, 2009 11:49 AM|chris555|LINK
I have the same issue. Each time I shut down my PC and reboot, then open VS 2008 Team up I get the same message! What is the fix MS?
Repeated "configuring the environment for first time use"
Aug 09, 2015 12:48 AM|jstubing|LINK
I'm getting the same issue six years later... Surely the workaround has come out by now.
Sep 25, 2015 01:05 AM|artbergquist|LINK
And I get the issue with Visual Studio 2005 running on a Windows XP virtual machine on Windows 7.
Sep 25, 2015 06:55 AM|PatriceSc|LINK
It seems expected the first time it runs under a particular account. My understanding is that you revert each time to a VM snapshot on which VS was never launched. Isn't it possible to take this snapshot once VS has been launched once? Seems more a VM handling