Should I add the Visual Studio . suo and . user files to source control . . . Best practices for Subversion and Visual Studio projects is a more generic question about this exact topic Also the accepted answer of it contains a link to official MSDN documentation, which describes in detail which files directories of VS solutions projects should be added to source control systems, and which parts should be ignored
What is actually contained in a *. suo file? - Stack Overflow 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
Why are there . sln, . suo and . csproj files? - Stack Overflow The solution maintains the state information for projects in sln (text-based, shared) and suo (binary, user-specific solution options) files … [Source] Furthermore, also from MSDN: The solution user options ( suo) file is a structured storage, or compound, file stored in a binary format
Best practices for editing sln, proj, suo files? - Stack Overflow In NET, there are SUO, SLN, Proj files for every solution project Whilst I know what these files are, is it wise to edit them by hand? Do they ever even need to be edited? If so, what is the best
c# - What is . wsuo file? - Stack Overflow 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
gitignore doesnt ignore . suo Visual studio file - Stack Overflow I want to do simple thing, ignore suo file and bin and obj folders from committing to git repo I've created gitignore file and it's working for bin and obj folders, but it keeps allowing suo file
git - Cant ignore . suo file - Stack Overflow We have added the entry "project1 suo" to the gitignore file but every time one of us has to commit the project, Git seems to tell us to commit the file "project1 suo" as well We have tried many methods to add the file in gitignore like that: * suo project1 suo c:\project\project1 suo How can we ignore the SUO file during the commit?
Where does VS 2022 store the last-used build variant? In this case, the suo file is in vs\project\v17 I originally didn't come to that idea because I always was assuming that a suo file is just a binary form of a sln file, for faster lookup or whatever, and because Microsoft recommends against putting it under source control: The solution user options ( suo) file contains per-user solution