text: ReSharper 6.0 Release Candidate has arrived! Please download and try the RC build, especially if the following improvements fix issues that you’ve had with Beta 3 or earlier Beta builds:
  - Additional memory consumption optimizations in addition to those introduced in Beta 3.
  - More performance fixes in ASP.NET MVC.
  - Fixes ensuring that all options are persisted between sessions.
  - Bug fixes and cosmetic improvements in unit test runner, specifically related to QUnit support.
  - Proper support for .NET Micro Framework and Windows Azure Toolkit for WP7.
  - Fixes ensuring that ReSharper 6 successfully starts under Windows XP SP3 with Visual Studio 2010.
  If any critical issues are still bothering you, this could be your last chance to report them and have them fixed before release!
  You’re going fast guys, do you ever sleep? ;-P
  @tc
  We do sleep – in turn
  In the beta 3 I had 4 issues where compiler errors were false positive or negative. I would recommend that you download the largest 10 solutions from codeplex and investigate all errors that you find. The solution analysis feature seems a little under-tested to me. My solution was only 50k LOC in size and I would have expected to find no bugs.
  What about a Machine.Specifications test runner?
  @tobi
  We’re testing R# features on quite a bit of different solutions. Can you create a sample solution for us that has the errors that you’re getting in your solution, or, if you’ve seen specific false positives in any of the projects available on codeplex, can you point us to them specifically?
  @David
  Alexander Gross is working on updating the MSpec plug-in for v6
  I have similar (same?) issues as tobi in the RC and the Beta 3.
  @Tobi, @Lazydev
  Guys, there’s exactly one way how you can help us fix the issue (issues?): that is, by providing a sample solution (leave alone the original solution) that would help us reproduce the false positives. If you’re able to do that, please do. Thank you.
  Any chance bug DOTP-2163 will get fixed in time for final release? I know this is filed under dotPeek but it is really a decompiler issue that ReSharper suffers from as well.
  @Justin
  Unfortunately this won’t make it to 6.0. There’s however a huge chance that it will be addressed in subsequent 6.x releases.
  Find Usages is giving incorrect results in R#6beta3 and R#6RC. Anywhere you use an object initializer, like:
  new MyClass { Name = “Foo” }
  R#6 doesn’t recognize that Name refers to MyClass.Name. If you find usages to a Name property on *any* class, even a class that’s completely unrelated to MyClass, the above would be shown as a hit.
  This is in YouTrack as RSRP-273111, along with a simple repro case.
  Thank you for the update, though. Maybe it will it at least make it into the final 1.0 release of dotPeek?
  @Justin
  I very much hope so – it is scheduled to be fixed for dotPeek 1.0 release.
  Just installed it, and I have to say you guys have done some tremendous work speeding everything up!
  dotCover and dotTrace (Performance), after you install ReSharper 6.0 RC, reported that are not compatible with it.
  When do you plan to release a compatible version of ReSharper 6.0?
  @Joe
  Thanks for the report, fixed yesterday
  @perry
  Glad to hear it’s working fast for you.
  @StarLancer
  dotCover 1.1.1 and dotTrace 4.5.1 with support for R#6 will be made available in a couple of weeks after R#6 release.
  did resharper.resharper_unittest_contextrun go away as a keyboard mapping option in resharper 6? is there an alternative way to be able to context run from the keyboard?
  thanks
  @Dave, I just use Alt+(R, U, R) to invoke it from the menu.
  thanks joe, i can certainly do that, even though it is less than ideal. can’t imagine why that would go away. if the keyboard mapping could be put back for the release, i’d be happy.
  I have installed the RC version and resharper is “Processing source files” every alternate second! This is slowing down the VS code editor and intellisense. Is there anything I need to do?
  @Hussain,
  What type of project is it? How big is it? Can you please contact me (hadi at jetbrains) with more information? We’d really like to solve the issue.
  Thanks.
  @Dave,
  It’s now ReSharper.ReSharper_ReSharper_UnitTest_RunContext
  It’s also mapped out of the box now with Ctrl+U, R
  @Husain
  Also please make sure to clean ReSharper caches by deleting YourSolutionName.suo and _ReSharper.YourSolutionName folder – this may help
  @jura: I uninstalled R#, deleted all the resharper folders from program files, app data and the cache folders in all my solutions but it did not help.
  @Husain
  We’ll need to take a look at your solution then, or a sample solution that reproduces the issue. Thank you
  @Hadi:
  “ReSharper.ReSharper_ReSharper_…”
  That’s just bizarre. Why so many ReSharpers? Shouldn’t the “namespace qualifier” (or whatever it’s called for VS commands) be enough for disambiguation?
  @Hadi,
  thanks, that’s what i needed. i’m surprised i didn’t find that on my own. confusing that the two context ones are segregated from the rest of the unit test invocation stuff, but as long as it’s there, everything is good.
  This question may have been asked already, but I’ll throw it out there myself.
  Will ReSharper 6.0 support the next version of Visual Studio (vNext)?
  @Alex
  ReSharper 6.0 won’t, further versions will