« Elder Scrolls IV: Oblivion – My quick thoughts - JohnChow.com: A great resource for bloggers. »

ReSharper issues on Windows Vista and VS2005

9 December 2006

For those of you who don’t know what ReSharper is, it is an Add-In for Visual Studio 2005 that vastly improves the poor refactoring support as well adds some useful functionality.

The First Problem:

I recently decided to take the Widows Vista plunge and installed it on a spare drive on one of my development workstations. In order to get it up to par with my needs I immediately installed VS2005 so that I can begin testing my existing applications as well as coding a few new ones. I’ve been using ReSharper since version 1 so it was the first thing I installed after getting VS2005 up and running.

Guess What? Things didn’t go quite as well as I would have hoped. Just as ReSharper was finishing installation, it erred out and rolled back the install.

I turns out that even though the install was running with elevated privileges it still was unable to update the os as it needed. This it turns out is not MS’s fault but rather the fault of the ReSharper installer. Apparently it doesn’t correctly assert which permissions it needs to execute successfully.

The Solution:

This is pretty simple but, it works. I just right-clicked on the installer an selected ‘Run as administrator’. At this point everything seemed perfect.

Another Problem:

At this point, I just wanted to verify the ReSharper install and get things configured to my liking. So, I fired up VS and I am greeted by a nice error from the ReSharper engine.

The Same Solution:

To get past this I had to do the same ‘Run as administrator’ trick. It works for now, but I am not sure how comfortable I am coding with elevated privileges; I have been preached at for the last 2 years not to.

I’ve submitted a bug report to the great folks over at JetBrains and hopefully this will get addressed in a future release.

Note: After closing VS2005 and later opening it without using the ‘Run as administrator’ option I did not get an error from ReSharper. Hopefully this part of the problem went magically into the night, but I highly doubt it.


Leave a reply