1

I have the unortunate sitation with using a source control tool that keeps my local files read-only if they are not checked out. When I attempt to apply a refactoring such as Move to Another Namespace using Resharper 6.1.1, it fails with the dialog

Resharper Recactoring Failure

because the other files in the solution are currently read-only. Is there a fix or workaround for this? If not I'll enter it into their issue tracker.

Kit
  • 20,354
  • 4
  • 60
  • 103
  • What source control system are you using? Could you checkout all the files in your solution/project before attempting this operation? – Piers Myers May 30 '12 at 12:00
  • It's Clear Case. Thankfully moving to TFS soon. Checking out the files or making them writeable is possible, but it causes Clear Case noise during the user experience, which is already painful. – Kit May 30 '12 at 16:20
  • I remember using Clear Case ages ago - I feel your pain :) TFS is not brilliant but at least it works well with refactoring. – Piers Myers May 30 '12 at 17:01
  • 1
    I had a similar issue that was caused by the new Git tools from microsoft. I blogged about it here: http://core-techs.net/Blog/161/resharper-refactoring-failed-caused-by-visual-studio-2012-tfs-git-provider – Ronnie Overby Feb 14 '13 at 19:00

1 Answers1

0

As a workaround, I would write a script to change read only property of the files. Depending on the IDE you're using you might be able to call such script in specific events like every build (supported by Visual Studio 2010).

Make read-only file read write from commandline windows

Community
  • 1
  • 1
fabiopagoti
  • 1,467
  • 14
  • 31