Should I add the Visual Studio .suo and .user files to source control ...
The solution user options (.suo) file is a structured storage, or compound, file stored in a binary format. You save user information into streams with the name of the stream being the key that will be used to identify the information in the .suo file … [Source] You do not need to put .suo file in VCS. That is a user-specific file.
Is there any way to view the contents of the solution user options file (the .suo file that accompanies solution files)? I know it's basically formatted as a file system within the file, but I'd li...
How to view the contents of the Solution User Options file (.suo)
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.