Configuration changes and multiple VS instances

I regularly work with multiple instances of VS open at the same time. If I then change any settings in R# I get a dialog asking me if I want to overwrite the configuration when closing all other VS instances. It would be a lot more helpful if R# would ask me to load the changed configuration into the other instances of VS instead when they are activated since I'm more likely to want the latest configuration.

Is it possible to change the default behavior?

4 comments
Comment actions Permalink

Hello,

No. The scenario could not be supported in the current architecture.


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


0
Comment actions Permalink

Hello appel,

I agree with you. Working with multiple instances of VS is a pain. I frequently
make changes to my R# options only to see them blown away by another instance
that I have open at the same time. Its hard for me to keep track of which
instance of the IDE I made the changes in, so I'm not sure whether to say
yes or no to it overriding the UserSettings.xml file when asked.

It would be great if JetBrains could address this issue in a future release.

~Andy

I regularly work with multiple instances of VS open at the same time.
If I then change any settings in R# I get a dialog asking me if I want
to overwrite the configuration when closing all other VS instances. It
would be a lot more helpful if R# would ask me to load the changed
configuration into the other instances of VS instead when they are
activated since I'm more likely to want the latest configuration.

Is it possible to change the default behavior?



0
Comment actions Permalink

Yes this issue is very annoying.

Is there a chance that you can fix this in the next version?

0
Comment actions Permalink

Hello Andre,

We have some plans to improve configuration system in one of the next versions.

Sincerely,
Ilya Ryzhenkov

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


IR> Yes this issue is very annoying.
IR>
IR> Is there a chance that you can fix this in the next version?
IR>


0

Please sign in to leave a comment.