Sharing code inspection settings across a team in resharper

Hi, I have seen a post about this back in January 2010, and the post indicated that this feature is on the backlog, but not for version 5. I was wondering if it made it into version 6? From what I can see it doesn't appear to have made it.

I think this option is essential, and would love to know when it is planed for?

Thanks.

12 comments
Comment actions Permalink

Hello Scott,

I'm afraid this functionality didn't make it into ReSharper 6. I'll write
back as soon as our plans regarding this functionality are finalized. Thank
you!

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

Hi, I have seen a post about this back in January 2010, and the post
indicated that this feature is on the backlog, but not for version 5.
I was wondering if it made it into version 6? From what I can see it
doesn't appear to have made it.

I think this option is essential, and would love to know when it is
planed for?

Thanks.

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



0
Comment actions Permalink

grumble... thanks for the quick response.

0
Comment actions Permalink

I think this is a highly sort-after feature - after all most programmers work in teams...

0
Comment actions Permalink

Other than bug fixes and performance improvements, this should be THE
feature that is being added.

We need to be able to share a bunch of settings across entire teams...
inspection settings being just one.  Code formatting being another.  We'd
really like to have ONE file that we can check in, and have ReSharper
reference, so that the settings are all in one place, every developer gets
them, and if there's a change, then every developer picks up the change on
the next 'get' from source control.

Additionally, I'd really like to see things like the abbreviations list
synchronized with the code analysis dictionary, so that we aren't
maintaining two lists of abbreviations and acceptable words.

Some clear guidelines about how to share these ReSharper settings across
teams, projects, etc. would also be very welcome.


"Andrew Serebryansky"  wrote in message
news:c8a898dd19e3f8ce09100e881c32@news.intellij.net...

Hello Scott,

I'm afraid this functionality didn't make it into ReSharper 6. I'll write
back as soon as our plans regarding this functionality are finalized. Thank
you!

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

Hi, I have seen a post about this back in January 2010, and the post
indicated that this feature is on the backlog, but not for version 5.
I was wondering if it made it into version 6? From what I can see it
doesn't appear to have made it.

>

I think this option is essential, and would love to know when it is
planed for?

>

Thanks.

>

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


0
Comment actions Permalink

I have to admit, as much as I really want sharing across team, at the mometn, I am finding
that the performance of Resharper 6 is so bad, that half of my team are refusing to run it
because it is soooo slow, so sharing across the team is uuseless until this is fixed.

0
Comment actions Permalink

That's why I started off the message with the phrase "Other than bug fixes
and performance improvements..."  :)

"Scott Baldwin"  wrote in message
news:22507755.358801311041005086.JavaMail.devnet@confluence.jetbrains.net...

I have to admit, as much as I really want sharing across team, at the
mometn, I am finding
that the performance of Resharper 6 is so bad, that half of my team are
refusing to run it
because it is soooo slow, so sharing across the team is uuseless until this
is fixed.

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

0
Comment actions Permalink

It looks like this was added in 6.1, but I still have a question that goes along with the feature that is requested above.  We want to share settings across all solutions for the whole team with one file.  It seems that you can do one or the other "easily".  In order to share across all solutions, you must store the .DotSettings file in AppData.  This obviously is not ideal for source control.  If you want to share settings with your team, you must do this on the solution level.  The, also, is not ideal if you have 80+ projects each with their own .sln.

For anyone who has started using 6.1, do you know of a satisfactory way to acheive using 1 file across the team for all solutions?  A thought would be to simply run a batch file that copies a single settings file to all solution directories OR just copy the AppData settings into a version controlled directory and manually copy it back into AppData each time a change is made.  Both of these would require manual notification to team members to update their settings which could be extremely troublesome for a 50+ member team if only 70% actually update.  

0
Comment actions Permalink

Hello Devin
     In order to have a single shared file for all solutions just add a new layer under 'This computer' (you can choose any location for that file), save all settings to be shared into that layer and put that layer file under version control. Other developers should just add that file as a layer under 'This computer' on their machines. Let me know if this helps. Thank you!

Andrey Serebryansky

Senior Support Engineer

JetBrains, Inc

http://www.jetbrains.com

"Develop with pleasure!"

0
Comment actions Permalink

Yeah, that makes sense.  Thank you!

0
Comment actions Permalink

Another question.  Supposed I add that file to source control in a root directory.  Then, per computer that needs to use it, I simply import the settings to the "This Computer" layer.  At that point does it do a one-time import of the setting and create the .dotSettings file in AppData or does it keep a dynamic link to the source-controlled file and auto-update every time that file is modified, i.e. will each developer have to re-import the settings with each modification?  

If the latter, is there a way to simply use a link to the source-controlled file in AppData to ensure settings are always up to date?

0
Comment actions Permalink

Hello Devin
     Actually, you do not "import" the settings file: you create a new layer under 'This Computer' group from your existing file (by clicking 'Add Layer' | 'Open Settings File'). This way, you permanently link this layer with your settings file. Whenever the file changes, those changes will automatically go into the corresponding settings layer in ReSharper. Moreover, you don't need to restart Visual Studio in order to apply new settings. Let me know if this helps. Thank you!

Andrey Serebryansky

Senior Support Engineer

JetBrains, Inc

http://www.jetbrains.com
"Develop with pleasure!"

0

Please sign in to leave a comment.