Answer by Pablo Carrasco Hernández for Should I add the Visual Studio .suo...
No. I just wanted a real short answer, and there wasn't any.
View ArticleAnswer by AntonK for Should I add the Visual Studio .suo and .user files to...
As explained in other answers, both .suo and .user shouldn't be added to source control, since they are user/machine-specific (BTW .suo for newest versions of VS was moved into dedicated temporary...
View ArticleAnswer by Stephen Kennedy for Should I add the Visual Studio .suo and .user...
No, they shouldn't be committed to source control as they are developer/machine-specific local settings. GitHub maintain a list of suggested file types for Visual Studio users to ignore at...
View ArticleAnswer by Amila for Should I add the Visual Studio .suo and .user files to...
Don't add any of those files into version control. These files are auto generated with work station specific information, if checked-in to version control that will cause trouble in other work stations.
View ArticleAnswer by adheen for Should I add the Visual Studio .suo and .user files to...
If you set your executable dir dependencies in ProjectProperties>Debugging>Environment, the paths are stored in '.user' files. Suppose I set this string in above-mentioned field:...
View ArticleAnswer by Farax for Should I add the Visual Studio .suo and .user files to...
On the MSDN website, it clearly states that The solution user options (.suo) file contains per-user solution options. This file should not be checked in to source code control. So I'd say it is pretty...
View ArticleAnswer by Stephen for Should I add the Visual Studio .suo and .user files to...
Since I found this question/answer through Google in 2011, I thought I'd take a second and add the link for the *.SDF files created by Visual Studio 2010 to the list of files that probably should not...
View ArticleAnswer by JXG for Should I add the Visual Studio .suo and .user files to...
Others have explained why having the *.suo and *.user files under source control is not a good idea. I'd like to suggest that you add these patterns to the svn:ignore property for 2 reasons: So other...
View ArticleAnswer by Fabio Ceconello for Should I add the Visual Studio .suo and .user...
These files contain user preference configurations that are in general specific to your machine, so it's better not to put it in SCM. Also, VS will change it almost every time you execute it, so it...
View ArticleAnswer by JRoppert for Should I add the Visual Studio .suo and .user files to...
No, you should not add them to source control since - as you said - they're user specific. SUO (Solution User Options): Records all of the options that you might associate with your solution so that...
View ArticleAnswer by ugasoft for Should I add the Visual Studio .suo and .user files to...
You cannot source-control the .user files, because that's user specific. It contains the name of remote machine and other user-dependent things. It's a vcproj related file. The .suo file is a sln...
View ArticleAnswer by Scott W for Should I add the Visual Studio .suo and .user files to...
This appears to be Microsoft's opinion on the matter: Adding (and editing) .suo files to source control I don't know why your project stores the DebuggingWorkingDirectory in the suo file. If that is a...
View ArticleAnswer by ScaleOvenStove for Should I add the Visual Studio .suo and .user...
I wouldn't. Anything that could change per "user" is usually not good in source control. .suo, .user, obj/bin directories
View ArticleAnswer by Thomas for Should I add the Visual Studio .suo and .user files to...
We don't commit the binary file (*.suo), but we commit the .user file. The .user file contains for example the start options for debugging the project. You can find the start options in the properties...
View ArticleAnswer by massimogentilini for Should I add the Visual Studio .suo and .user...
They contain the specific settings about the project that are typically assigned to a single developer (like, for example, the starting project and starting page to start when you debug your...
View ArticleAnswer by benefactual for Should I add the Visual Studio .suo and .user files...
These files are user-specific options, which should be independent of the solution itself. Visual Studio will create new ones as necessary, so they do not need to be checked in to source control....
View ArticleAnswer by titanae for Should I add the Visual Studio .suo and .user files to...
Using Rational ClearCase the answer is no. Only the .sln & .*proj should be registered in source code control. I can't answer for other vendors. If I recall correctly, these files are "user"...
View ArticleAnswer by Nick for Should I add the Visual Studio .suo and .user files to...
.user is the user settings, and I think .suo is the solution user options. You don't want these files under source control; they will be re-created for each user.
View ArticleAnswer by cori for Should I add the Visual Studio .suo and .user files to...
By default Microsoft's Visual SourceSafe does not include these files in the source control because they are user-specific settings files. I would follow that model if you're using SVN as source control.
View ArticleAnswer by Bloodhound for Should I add the Visual Studio .suo and .user files...
Visual Studio will automatically create them. I don't recommend putting them in source control. There have been numerous times where a local developer's SOU file was causing VS to behave erratically on...
View ArticleAnswer by Steve Cooper for Should I add the Visual Studio .suo and .user...
You don't need to add these -- they contain per-user settings, and other developers won't want your copy.
View ArticleShould I add the Visual Studio .suo and .user files to source control?
Visual Studio solutions contain two types of hidden user files. One is the solution .suo file which is a binary file. The other is the project .user file which is a text file. Exactly what data do...
View ArticleAnswer by Drew Noakes for Should I add the Visual Studio .suo and .user files...
Others have explained that no, you don't want this in version control. You should configure your version control system to ignore the file (e.g. via a .gitignore file).To really understand why, it...
View Article
