Quando parliamo di Albert Einstein, inevitabilmente la nostra mente viaggia verso equazioni complesse, alla rivoluzionaria teoria della relatività e all'immagine iconica dello scienziato dai capelli ...
Should I add the Visual Studio .suo and .user files to source control ...
Basically the suo file (i.e., Solution User Options) contains the information related to to a user level customization like breakpoints, bookmarks, Outlining, debugger watches etc. Also note that if you delete the suo file then Visual Studio will create a new one.
From official MS Docs: The solution user options (.suo) file contains per-user solution options. This file should not be checked in to source code control. The solution user options file is used to store user preference settings, and is created automatically when Visual Studio saves a solution. So need to worry. Even if you delete this, it will be auto generated on the very next build ...
In most cases, it does make sense to have a default on this. It would be much better to accommodate a default startup project and store this in the .sln file, but which can be overridden by a developer in their .suo file. If the startup setting isn’t found in the .suo file, the default startup project in the .sln would be used. Actually, this has been suggested on Visual Studio’s UserVoice.
I noticed that Visual Studio 2022 has a new method to store the opened documents in a DocumentLayout.json file rather than the old .suo file and it didn't migrate it to the new version. Am I the only person who lost his opened documents because of migrating from old Visual Studio?