Team shared shared setting confused when used with multiple source trees - absolute path

Hi,

When I add team shared solution settings in the same folder as the solution it creates a settings file (XXX.sln.DotSettings) file with an absolute path and an empty relative path. I have many source trees for different releases and different work items. So, Resharper is often using the setting file in another copy of the source, perhaps for a release that went out years ago. Editing changes the setting file in the other folder and are lost (do not go in with commit).

Also, Resharper sometimes creates the path described in the absolute path if it does not exist.

Sometime it also just changes the absolute path if opened using another path ... hence a commit change.

This is making the feature difficult to use. How can I make it use a relative path only so it will not pick up setting files in some other (last edited in) folder?

I can see that there have been several posts about absolute paths & setting layers and the reply has been 'no known scenario where this is a problem". Here I have a clear problem when I have multiple copies/versions of the source tree.