Code Style Sharing file name

We're starting to share code styles, so I've enabled the Shared across the team, per solution option. It's created a file in my solution root called Solution.Name.5.0.ReSharper. This is fine as I'm using v5.0 (5.0.1659.36).

In the documentation, though, it tells me I should expact a file called Solution.Name.ReSharper

  • Is this a problem?
  • What will happen if/when ReSharper's version number increases?
  • If I rename the file, will it still get picked up?


thanks.

2 comments
Comment actions Permalink

Hello Chris,

  • There's actually a mistake in documentation and we will fix that soon.

The file name should be .resharper.

  • If ReSharper version number increases, the new version will create a new

settings file

  • There's no automatic code style upgrade functionality in ReSharper, so

if you rename the file the result may be unpredictable.

Andrey Serebryansky
Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

We're starting to share code styles, so I've enabled the +Shared
across the team, per solution+ option. It's created a file in my
solution root called Solution.Name.5.0.ReSharper. This is fine as I'm
using v5.0 (5.0.1659.36).

In the documentation, though, it tells me I should expact a file
called Solution.Name.ReSharper

  • Is this a problem? * What will happen if/when ReSharper's version

number increases? * If I rename the file, will it still get picked up?

thanks.

---
Original message URL:
http://www.jetbrains.net/devnet/message/5264745#5264745



0
Comment actions Permalink

Hello,

Actually, previous versions of R# were writing the file without the version
number. As the file contents changed with versions, it started causing problems
if the same solution was opened with different ReSharper versions.

If I rename the file, will it still get picked up?


A specific ReSharper version always writes its settings into the same file.
While reading the settings, that file is also preferred, but files of previous
versions could be considered if the preferred one is missing. So the file
to add to SCC is the versioned one anyway.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Please sign in to leave a comment.