| Author |
Topic  |
|
|
foxmuldr
Tomato Guru
    
USA
439 Posts |
Posted - Nov 11 2025 : 2:52:23 PM
|
Is VAX only available in one instance of Visual Studio? I've noticed several times when the keyboard shortcuts only work in the first instance launched. Even after I close it, the keystrokes still don't work in the other ones.
-- Rick C. Hodgin
|
|
|
feline
Whole Tomato Software
    
United Kingdom
19279 Posts |
Posted - Nov 12 2025 : 08:05:05 AM
|
I am normally working with several instances, and different versions, of Visual Studio open at the same time. This does not sound like anything I have seen before.
VA saves out its settings when you close the IDE, so if you make changes in one instance, and then close the instances in the "wrong" order the changes will be saved out, then overwritten. Not sure how this could lead to this, but it is an odd effect you can see with multiple instances. |
zen is the art of being at one with the two'ness |
 |
|
|
foxmuldr
Tomato Guru
    
USA
439 Posts |
Posted - Dec 09 2025 : 12:22:25 PM
|
| I still see it in Visual Studio 2022 Enterprise, Professional, and Community versions, on three separate machines. It's sporadic, but at times it will only work in the first instance, and not in the second or later. I've also seen it where it stops working outright, and keyboard shortcuts that VAX normally intercepts then fall through as though VAX wasn't enabled. |
 |
|
|
feline
Whole Tomato Software
    
United Kingdom
19279 Posts |
Posted - Dec 10 2025 : 08:01:45 AM
|
How are you loading the instances? Any command line switches? Opening by double clicking on a SLN file?
Is the problem somehow solution specific?
Any obvious common factors across all of these machines? Another extension, an unusual utility that you installed?
Checking with a test profile with only VA installed and active as an installed extension would be the next logical step. Which version of VA are you currently using? |
zen is the art of being at one with the two'ness |
 |
|
| |
Topic  |
|