Is this going to be targeted for 6.0? This is a very important feature to me.

created 3 years ago? wow...

We would upgrade from 5 to 6 for this feature.

EAP for 6.1 with this feature will be opening this fall.

First builds will allow sharing any setting across the solution file – not exactly sharing with the external file yet, but still fitting most of the needs (I hope). External files will follow. It would help us if you comment on your scenarios involving the manually-defined external file rather than sharing the settings along with the solution.

We do not use solution (sln) files to manage our projects. Instead each developer creates their own solution file and loads only the assemblies they need - visual studio (and resharper) respond much faster that way. Because of that, having settings saved/shared across via the solution file is really what we are looking for.

For us, it would be helpful to have settings declared in a file and each time visual studio starts it could read in the most recent settings. That would keep things consistent across projects.

Jeff: settings are not written into right the solution file (otherwise any external settings change would have resulted in a solution reload, which is undesirable). This separate file could still be shared, even though the .sln file is unique to each machine.

Thanks Serge. If we can create one settings file that we check in with our source code and everyone can automatically get updates when they get the latest version of code then I will be happy :)

We would be looking to create a single file that could be applied to all solutions and shared it in revision control. I should be able to point ReSharper to where it is synched on my machine and any time it changes ReSharper should pick up new settings. We are trying to create a uniform set of rules/inspections/settings to apply across all solutions.

Oleg: could you please expand on the scenario?

You need the solution file to point to some settings file, same one for everyone and for all solutions. This reference should be stored along with the solution in the source control. Right?

Now, the shared file. Is it expected to be in source control also (in some location common for all solutions), or on a UNC path to a network share, or on each developer's computer locally?

Serge:

We need ReSharper to point to some settings file, not solution (although the latter could be useful for custom settings for a particular solution to overwrite the settings in the ReSharper settings file).

Yes, the shared file will be in source control in a common location. Once the developers sync their computer, they should be able to navigate from some ReSharper options menu to this file. If the contents of the file change, ReSharper should refresh the settings immediately without having to restart Visual Studio.

Perhaps our scenario is slightly different from others. Basically, I'm looking for a way to share settings without solutions knowing/storing any ReSharper info at all. I simply want to point ReSharper to one file and apply those settings to any solution I open, regardless of whether they are in source control or not. Does that make sense?

Oleg:

This makes strong sense if you got more solutions than developers. You'll be able to add a settings file as a layer to the settings system on each of the computers and have it behave the expected way.

In case there are more developers than solutions (which is also quite common), it might be easier to do the setup once per solution rather than once per machine, and that's what I meant in the previous comment.

We're not exposing UI for adding new layers in the first EAP build though – to focus on basic operations with predefined layers which are global settings and solution settings of the solution currently loaded.

Thanks, Serge. Our case is few developers, many solutions. We will inpatiently wait for the EAP with global settings!

If it could work like Settings.stylecop (including relative positioned merged files) file it would be perfect (for me).

I'm sorry but I'm unable to get any valuable result from this new 6.1 system – is there any documentation about it? Why are the "Move Up", "Move Down" and "Mount to" buttons always disabled? Which is the precedence? Has to top item highest priority or the bottom one? Why are the "save" and "save to" buttons always closing the dialog? Which sense does it make? (I edited "File Header Text" option and clicked on "Save To Solution-shared-with-team" : The dialog closed, and on reopen the old setting was there again).
And what is "Solution.6.1.resharper" file still for?

We're going to publish a blogpost on the settings quite soon.

Serge -

I wanted to chime in to say that the situation Oleg describes is exactly what I am looking for as well. We have many more solutions than that developers; also developers make ad-hoc solutions regularly here. We do have a developer setup script which can point Resharper at a standard location.

So what I want (and my original desire behind opening this ticket) is to get support for what Oleg describes.

Thanks

I think the current EAP versions are good enough around this functionality, and their quality is acceptable.