I work on a solution containing around 35 projects, including a few Silverlight projects, a web server a rich client and the rest are libraries. I'm using VS2010 (V10.0.30319.1 RTMRel) on Windows 7 Prof (V6.1..7600)
My problem is that it takes between 30 and 60 seconds (and sometimes more) to close a single open editor file. This is always the case, and is independent of the number of files open in VS at the time. This is obviously a pretty crippling delay to endure while developing.
While the file closes the circular 'hourglass' cursor is displayed and VS becomes 'Not Responding'. When closing a number files in sequence they each encounter the delay.
Closing 'all files but this one' results in a magnification of the issue: The total wait depends upon the number of open files, but can take many minutes to complete. The issue also occurs when closing the solution as, I assume each open file is separately closed.
I've tried to use the VS Performance tool (PerformanceDiagnostics.exe) I've seen mentioned on the forums, but when I try start a profile against the devenv process the 'Starting XPerf profiling. Please wait' message sits indefinitely and the profiling does not start.
I've also generated a trace file manually using xperf buy: Opening my solution in VS, starting the xperf trace, closing a single file, and dumping the xperf etl file. The problem is I'm not sure how to evaluate the results. I can see what looks significant amounts of disk IO (between 200 and 600 'counts' for 80% of the trace time) which seems unusual (the total time taken to close the file in this case was around 50 seconds).
It may be relevant that I've got Resharper installed, although I have tried disabling it and it did not solve the problem.
Is this a know issue? Is there any fix for this?