History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RSRP-51060
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Serge Baltic
Reporter: Evgeny Potashnik
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ReSharper

Changes to version-control .resharper file can get overwritten

Created: 15 Oct 07 08:00   Updated: 24 Apr 08 16:09
Component/s: Options
Fix Version/s: Aroha
Security Level: Everybody (All jira users)

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

Build: 517


 Description  « Hide
We have a solution that several developers work on, which is stored in Subversion, including its .resharper file. Once in a while a developer makes some R# configuration change, eg. adding a LiveTemplate and commits it to SVN, but the change is "undone" in a subsequent commit by another developer (eg. the LiveTemplate is deleted). I believe that this is happening, because developers often update their working copies of the code from SVN with the solution open in VS.NET (there is normally no need to close it, because VS.NET automatically detects any changes), then at some later point R# saves its own configuration from memory to the .resharper file, overwriting the changes retrieved from source control.

This really needs to be handled better. Ideally R# should watch for changes to the file and reload it when it changes, but apply any locally made changes to the updated file. Eg. if open the solution, add a new LiveTemplate, do an SVN Update which also adds a LiveTemplate then the updated file should contain both of them. If this cannot be done then R# should at least inform the user of what happened and let them manually merge the file. It should not lose any changes in any case.



 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.