ReSharper renaming and read-only flags

[themarsvoltaire]

If I rename a c# class in my Plastic controlled project with ReSharper in Visual Studio 2013, it renames the file itself (resulting in a pending move in the workspace) and also modifies the contents of the file with the new class name. If I work in the read-only files checkout workflow, it fails to save the modified contents of the file because it is set to read-only. Normally editing a file's contents checks it out and unlocks it, but I guess the file rename isn't doing it or there is some other weird interaction going on between ReSharper and the Plastic SCM plugin.

 

I don't mind switching to the no checkout workflow without read-only files for now as a workaround, but this didn't seem like the intended behavior when I encountered it and might be a problem for others who have to stay with the read-only files checkout workflow.