Warning: ReSharper 5.0 can corrupt VS 2010RTM ability to change Target FrameWork

I was pretty sure this was a MS VS 2010 bug, and reported it to MS here :


Turns out: un-installing the trial version of ReSharper 5.0 took care of this problem.

So, if you are using VS 2010 RTM, and ReSharper, and find you cannot switch the target FrameWork from its default (FrameWork 4.0 Client) to any other FrameWork without a strange error message dialog involving an "invalid xml file" and some entity called "TargetFrameWorkMoniker" : the problem is with ReSharper.

I hope you don't lose the amount of time and $ I did.

best, Bill

Please sign in to leave a comment.