Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Visual Studio freezes often when solution is opened from network [closed]

I'm having an issue where Visual Studio performance is horrendous when the solution is loaded from a networked drive. This does not seem to happen to other developers, just me.

After running procmon and monitoring the devenv process, i notice that one key difference between a project opened from a local path vs a networked path is that the project opened from the networked path is trying to execute Operation 'CreateFile' on path 'C:\Windows\CSC\v2.0.6\namespace\kpg.apps' 1000s of time. the Result is 'NAME NOT FOUND'.

Does anyone know why visual studio is trying to do this for the project opened from the network and how i can resolve or at the very least stop it from attempting this operation?

thanks

like image 505
mike01010 Avatar asked May 23 '13 15:05

mike01010


2 Answers

It may help to disable offline files (which are stored by default at the location you mentioned): Go to control panel, Sync Center to manage that.

Also, some servers may be configured to force offline files on the share - but this may not be the case when it works for other users.

like image 196
JeffRSon Avatar answered Oct 17 '22 19:10

JeffRSon


It sounds like you have either:

  1. An overactive virus scanner or external application interfering with Visual Studio
  2. or, a heinous add-on/extension for Visual Studio

The easiest way to determine which of these two is to open the solution in Safe Mode, which you can do from a Visual Studio Command Prompt:

Setting environment for using Microsoft Visual Studio 2010 x86 tools.
X:\>devenv /safemode \\unc\path\to\your\solution.sln

This will turn off all the bells and whistles while loading your solution.

If it is still slow, this is most likely not a Visual Studio problem. Keep in mind though that network resources and Windows rarely play well together. Numerous "trust" settings affect the behavior of files loaded from UNC paths.

That folder is Windows Client Side Caching, so this is not a VS problem.

like image 45
user7116 Avatar answered Oct 17 '22 19:10

user7116