title: Resharper 8.1 Test Runner slowing down Visual Studio Text Editing
body: <p>I've got a fairly small C# solution with about 5 projects in it. I am using Visual Studio 2012 with Update 4, and Resharper 8.1 (build 8.1.23.546). It's on an I7 with an SSD and 16GB RAM, with oodles of disk space. Performance on this machine is fantastic for everything else.</p>
  
  <p>I have R# set to be my unit test runner, and I've noticed that as soon as I run any unit tests (one or many, pass or fail, makes no difference), the Visual Studio text editor becomes almost unusable. Typing into the editor window suffers such extreme lag (up to 1 second between keystrokes) that it completely breaks down the development flow. Sometimes I actually have to stop typing to let the keystrokes catch up so that I can look up something in Intellisense.</p>
  
  <p>The problem persists until I close down and then reopen VS, at which point everything is fine again. Until I run another unit test. Then it's back again.</p>
  
  <p>I've run Process Monitor to see if that turned up anything (it didn't), and I've tried various things like cleaning out various caches, temporary asp.net files, resetting settings, all to no effect, in fact basically pretty much all the options presented at <a href="http://www.google.com.au/search?q=Visual%20studio%202012%20typing%20really%20slowly" rel="noreferrer">Google search results for VS being really slow</a></p>
  
  <p>However, process of elimination did eventually narrow everything down to being a problem with Resharper, and specifically the test runner. </p>
  
  <p>I then tried the R# performance optimisation tips as described <a href="http://confluence.jetbrains.com/display/NETCOM/Ultimate+Guide+to+Speeding+Up+ReSharper+%28and+Visual+Studio%29" rel="noreferrer">here - The Ultimate Guide to speeding up Resharper</a>, and the only one that worked (after many restarts) was the disabling the Unit Test Runner.</p>
  
  <p>I've since disabled the R# test runner, and reverted to the built-in VS one (which I hate), and the problem went away immediately. As soon as I re-enable the R# test runner, the problem comes back.</p>
  
  <p>Has anyone else experienced this problem, and found a solution?</p>
  
  <p>Cheers :)</p>