issues and workarounds

First of all, dotCover 1.1 RC and dotTrace 4.5 Performance RC builds are available starting today. We've fixed a couple of issues since Beta 2 builds, such as buttons not working in some cases in dotCover's Show Covering Tests pop-up, inaccurate system requirements check in dotTrace, and a pack of exceptions. Please help us verify that these release candidates are OK for public releases later this month. If you face any serious bugs, please use the dotCover issue tracker and dotTrace issue tracker to report them. There's also something we should make you aware of regarding using dotCover 1.1

Derick Bailey pointed out today on Twitter that during an upgrade, he lost his ReSharper templates.   ReSharper should import the existing templates during an upgrade. However, for some odd reason, sometimes this does not occur. We managed to sort out Derick’s issue relatively quickly, but in case others might run into the same problem, here’s how to solve it: Scenario: Upgrading from 5.0 to 5.1 in VS2010 and settings lost. 1. Close down Visual Studio 2010. 2. Go to the %AppData%JetBrainsReSharper folder. In there you should find subfolders for each version of ReSharper. Select v5.

Users keep coming with questions whether a particular issue that they encounter in Visual Studio is related to ReSharper. Well, some of them are, some of them aren't. Either way, we try our best to provide info on workarounds for common issues, both our own and external, in this blog post. Check it out for latest updates on GetTempFileName()-related exceptions in certain versions of Windows, and "insufficient memory" messages caused by simple cut-and-paste operations in Visual Studio — both issues fortunately not in any way related to ReSharper. As to ReSharper's own issues, we keep fix

Hello everyone! Hope you're having a good time using the new ReSharper 5.0. If you do, just ignore this post :) If you're facing issues with ReSharper 5.0, read on. There are certain bugs, usability problems and otherwise weird behavior that users report following the release (surprise!). Some of them you can work around, others you can't, but both kinds of issues will be addressed in the upcoming ReSharper 5.1. It's scheduled for release in June but we'll open the Early Access Program in May, and chances are that the most annoying issues will be fixed in these early builds. Here are so