neb:Behodar:This has been going on for years as Microsoft focuses on adding bling at the expense of maintenance. I've had bugs, as in regressions, "worked in VS 201x but stopped working in 201y", in VS open for years that never get fixed. I'm lucky enough that I can keep using very old versions for development and only do release builds in the latest version. Which also keeps showing me how much of an improvement older versions are on their successors.
Argh. Software bugs again. The "find in files" feature in Visual Studio 2022 refuses to work in a specific project (it just happily tells me that it's searched 0 files). Other projects work fine, and the 'bad' project works fine in Visual Studio 2019. No idea what's going wrong here...
One of my 'favourites' was when I logged a bug in VS Mac (although the issue I mentioned yesterday was Windows). The Close button only hid the app and didn't actually close the file/project.
For those not familiar with MacOS, normally closing a window will retain the app's menu bar and will obviously close the document, whereas hiding an app will switch the menu bar back to the previous app you were working in, and clicking/tabbing back to the original app will restore the document without any changes.
So, Visual Studio was performing the wrong action when you clicked the Close button. I logged a bug and Microsoft came back with something to the effect of "this has been broken for so long that we don't want to fix it because it'll confuse anyone who relies on the broken behaviour".
Probably still better than Apple Xcode though, which, when closing a file, automatically saves it then asks whether you want to save. Whether you click Save, Don't Save or Cancel at this point is irrelevant because it's already been saved. Bug reported to Apple nine months ago and not fixed yet.

