VS2022
Re topic https://cplusplus.com/forum/lounge/283541/
[closed so I can't add a new post. Ahh...]
VS2022 17.3.0 has now been released which fixes these issues and a whole lot more
https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-notes#17.3.0
[closed so I can't add a new post. Ahh...]
VS2022 17.3.0 has now been released which fixes these issues and a whole lot more
https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-notes#17.3.0
MS does it again, changing some behavior with a new release.
Inline hints before 17.3.0 were/are nice, controllable to toggle using the CTRL key making 'em appear and disappear as needed.
Now with 17.3.0 the "magic key" for toggling inline hints is ALT + F1. boo!
Even worse is there is no mention of how to toggle the hints from any of the VS menus, you have to go Tools -> Options and do a search.
Or "hover" your pointer over the inline hint for a couple of seconds. Not. Cool. Behavior.
Inline hints before 17.3.0 were/are nice, controllable to toggle using the CTRL key making 'em appear and disappear as needed.
Now with 17.3.0 the "magic key" for toggling inline hints is ALT + F1. boo!
Even worse is there is no mention of how to toggle the hints from any of the VS menus, you have to go Tools -> Options and do a search.
Or "hover" your pointer over the inline hint for a couple of seconds. Not. Cool. Behavior.
Last edited on
That's MS for you!
Why don't you install the VS2022 preview version and try out what's coming down the line? It's much easier to get things that 'don't work as expected' changed in a preview version than once its a proper release - just report as a bug!
VS2022 17.4 preview 1 is now available.
Apart from some further support for C++23 library functionality, one of it's main new 'features' is the ability to roll-back updates to the previous version.
https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-notes-preview
Why don't you install the VS2022 preview version and try out what's coming down the line? It's much easier to get things that 'don't work as expected' changed in a preview version than once its a proper release - just report as a bug!
VS2022 17.4 preview 1 is now available.
Apart from some further support for C++23 library functionality, one of it's main new 'features' is the ability to roll-back updates to the previous version.
https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-notes-preview
Last edited on
Nah, I prefer to not deal with potential preview issues and differences in work-flow. As fooked up in minor house-keeping details as each new release can be from previous ones having to remember which version requires what key-strokes or menu clicks to do something would be frustrating. Especially for this "having a senior moment" old fart.
I used to be able to start a new project, copy some code files into the solution/project dir where the configuration files are placed and then add those existing files to the project. That was possible, the first place VS searched was for files was the local dir.
Not any more. Now it is an external repos dir by default. No way that I can find to return to the old behavior I got very used to. GRRRR!
Now I have to add new, blank code files so they are placed in the proper dir and copy over those blank files with my pre-existing code files.
I used to be able to start a new project, copy some code files into the solution/project dir where the configuration files are placed and then add those existing files to the project. That was possible, the first place VS searched was for files was the local dir.
Not any more. Now it is an external repos dir by default. No way that I can find to return to the old behavior I got very used to. GRRRR!
Now I have to add new, blank code files so they are placed in the proper dir and copy over those blank files with my pre-existing code files.
As "down on VS/MS" as my kvetching might seem to be, I ain't.
Honest.
I remember the days when someone wanting to do programming on Windows with an MS compiler/IDE was a "ya gotta buy it" situation. Big Bucks Expensive, get a used copy with no support....or pirate a copy of VS 6.
Then MS brought out their Express versions that were great but lacked some key features.
With VS being feature rich beginning with the 2015 editions VS is now more useful than ever despite the ham-fisted hoo-man boo-boos.
So with each new update I have to relearn my keyboard ninja ways of doing things. meh.
Small price to not pay with the Community edition. :Þ
Honest.
I remember the days when someone wanting to do programming on Windows with an MS compiler/IDE was a "ya gotta buy it" situation. Big Bucks Expensive, get a used copy with no support....or pirate a copy of VS 6.
Then MS brought out their Express versions that were great but lacked some key features.
With VS being feature rich beginning with the 2015 editions VS is now more useful than ever despite the ham-fisted hoo-man boo-boos.
So with each new update I have to relearn my keyboard ninja ways of doing things. meh.
Small price to not pay with the Community edition. :Þ
Topic archived. No new replies allowed.