Question Visual Studio 2022 Undo/redo not working

[cbreemer]

Just had a bit of a scare, while working on a C# file in VS2022. I buggered something up wit cut/paste, did not remember exactly what was there before I screwed up, so I pressed Ctrl-Z. Nothing happened Went to the Edit menu and behold, all the Undo and Redo functions were greyed out.
I then realized that I had 2 instances of VS2022 running. In the other one, Undo/Redo worked fine. I shut down that other one but that did not make it work in the active one. Only after I restarted that instance, things were back to normal.
Not a big deal now that I know, but does this make sense somehow ? Would this be a bug or a feature ?

 

[Skydiver]

Sounds like a bug. Undo/redo should be on a per instance implementation.

 

[cbreemer]

Sounds like a bug. Undo/redo should be on a per instance implementation.

Thanks, I thought so too. I better report it, surely MS will be eager to fix it

 

[jmcilhinney]

You'll need to make sure that you can reproduce it consistently before a report will be considered. If Microsoft can't reproduce it, they won't (can't) try to fix it. Given that I've never seen that behaviour and haven't heard anyone else describe it, it's also likely that others won't be able to reproduce the behaviour you're seeing with the same steps you take. I would suggest that you start by repairing VS as it may be due to some corruption somewhere.

 

[cbreemer]

You'll need to make sure that you can reproduce it consistently before a report will be considered. If Microsoft can't reproduce it, they won't (can't) try to fix it. Given that I've never seen that behaviour and haven't heard anyone else describe it, it's also likely that others won't be able to reproduce the behaviour you're seeing with the same steps you take. I would suggest that you start by repairing VS as it may be due to some corruption somewhere.

Yes thanks, of course I will make sure it is consistently reproducible before submitting this. Given Microsoft's track record of addressing customer issues, I do wonder if it is worth the trouble though....

 

[Skydiver]

If do manage to reproduce, it the way to report the issue not to do a narrative like in the beginning of this thread, but rather follow this reporting format:

Short Description
Basically say what is broken. Assume that this will become a thread title.

Steps to reproduce:
1. Put numbered concise steps a that a 5 year old can follow.
2. Be precise about what buttons are pressed.
3. If needed describe what is shown on screen at that point in the steps and/or screenshots.

Results:
Described the result, error, or behavior that you got.

Expected results:
Described the result or behavior you were expecting to see.

Workarounds:
If you found a workaround, describe what you do.

Detailed description:
If the steps, results, and expected results require more detailed discussion, put the here.

Environment Details:
What OS?
What version of the OS?
What application(s)?
What version of the application(s)?
If relevant, screen resolution and/or color scheme.
If relevant, network connection type/configuration.

You might get more traction with MS if you report an issue in the format that is similar what they use internally. Also if you can put into the User Voice community you might also get some up-votes which could potentially also get MS's attention.

 

[cbreemer]

If do manage to reproduce, it the way to report the issue not to do a narrative like in the beginning of this thread, but rather follow this reporting format:

Short Description
Basically say what is broken. Assume that this will become a thread title.

Steps to reproduce:
1. Put numbered concise steps a that a 5 year old can follow.
2. Be precise about what buttons are pressed.
3. If needed describe what is shown on screen at that point in the steps and/or screenshots.

Results:
Described the result, error, or behavior that you got.

Expected results:
Described the result or behavior you were expecting to see.

Workarounds:
If you found a workaround, describe what you do.

Detailed description:
If the steps, results, and expected results require more detailed discussion, put the here.

Environment Details:
What OS?
What version of the OS?
What application(s)?
What version of the application(s)?
If relevant, screen resolution and/or color scheme.
If relevant, network connection type/configuration.

You might get more traction with MS if you report an issue in the format that is similar what they use internally. Also if you can put into the User Voice community you might also get some up-votes which could potentially also get MS's attention.

Thanks for that. Obviously I'd write a bug report much different than a casual question in a forum, but this is very useful information.

 

[cjard]

More importantly, learn what "git" is and how to use it ..