Should I add the Visual Studio .suo and .user files to source control?

Visual Studio remedies have 2 sorts of surprise customer documents. One is the remedy .suo documents which is a binary documents. The various other is the task .user documents which is a message documents. Specifically what information do these documents have?

I've additionally been asking yourself whether I need to add these documents to resource control (Subversion in my instance). If I do not add these documents and also an additional programmer checks out the remedy, will Visual Studio instantly create new customer documents?

2022-06-25 03:05:08
Source Share
Answers: 14

Others have actually clarified why having the *.suo and also *.user documents under resource control is not an excellent suggestion.

I would certainly such as to recommend that you add these patterns to the svn:ignore building for 2 reasons:

  1. So various other programmers will not end up with one programmer is setups
  2. So when you watch standing, or devote documents, those documents will not mess the code base and also rare new documents you require to add
2022-06-30 00:09:36

No, you need to not add them to resource control given that - as you claimed - they are customer details.

SUO (Solution User Options): Records every one of the alternatives that you could relate to your remedy to make sure that each time you open it, it consists of modifications that you have actually made.

The.user documents has the customer alternatives for the task (while SUO is for the remedy) and also expands the task documents name (e.g, anythingcsproj.user has customer setups for the anything.csproj task).

2022-06-25 03:59:07

I would not. Anything that can transform per "user" is generally bad in resource control.suo,. customer, obj/bin directory sites

2022-06-25 03:55:25

You can not resource - control the.user submits, since that is customer details. It has the name of remote equipment and also various other customer - reliant points. It is a vcproj relevant documents.

The.suo documents is a sln relevant documents and also it has the "solution customer options" (start-up task (s), windows placement (what is anchored and also where, what is drifting), etc)

It is a binary documents, and also I do not recognize if it has something "user related".

In our firm we do not take those documents under resource control.

2022-06-25 03:54:19

This seems Microsoft is point of view on the issue:

Adding (and editing) .suo files to source control

I do not recognize why your task shops the DebuggingWorkingDirectory in the suo documents. If that is a customer details establishing you need to take into consideration saving that in the *. proj.user filename. If that setup is shareable in between all customers working with the task you need to take into consideration saving it in the task documents itself.

Do not also consider including the suo documents to resource control! The SUO (soluton customer alternatives) documents is suggested to have customer - details setups, and also need to not be shared among customers working with the very same remedy. If you would certainly be including the suo documents in the scc data source I do not recognize what various other points in the IDE you would certainly damage, yet from resource control perspective you will certainly damage internet tasks scc assimilation, the Lan vs Internet plugin made use of by various customers for VSS accessibility, and also you can also create the scc to damage entirely (VSS data source course saved in suo documents that might stand for you might not stand for an additional customer).

Alin Constantin (MSFT)

2022-06-25 03:52:20

These documents have customer choice arrangements that remain in basic details to your equipment, so it is much better not to place it in SCM. Additionally, VS will certainly transform it virtually every single time you execute it, so it will certainly constantly be noted by the SCM as 'transformed'. I do not include either, I'm in a task making use of VS for 2 years and also had no worry doing that. The only small aggravation is that the debug parameters (implementation course, release target, etc) are saved in among those documents (do not recognize which), so if you have a criterion for them you will not have the ability to 'release' it using SCM for various other programmers to have the whole growth setting 'all set to make use of'.

2022-06-25 03:51:56

You do not require to add these - - they have per - customer setups, and also various other programmers will not desire your duplicate.

2022-06-25 03:15:59

Visual Studio will instantly create them. I do not advise placing them in resource control. There have actually been countless times where a neighborhood programmer is SOU documents was creating VS to act unevenly on that particular programmers box. Removing the documents and afterwards allowing VS recreate it constantly dealt with the concerns.

2022-06-25 03:15:55

By default Microsoft is Visual SourceSafe does not include these documents in the resource control due to the fact that they are customer - details setups documents. I would certainly adhere to that version if you are making use of SVN as resource control.

2022-06-25 03:15:11

. customer is the customer setups, and also I think.suo is the remedy customer alternatives. You do not desire these documents under resource control ; they will certainly be re - developed for each and every customer.

2022-06-25 03:15:06

These documents are customer - details alternatives, which need to be independent of the remedy itself. Visual Studio will certainly create new ones as essential, so they do not require to be signed in to resource control. Without a doubt, it would possibly be far better not to as this permits specific programmers to tailor their setting as they please.

2022-06-25 03:14:58

We do not devote the binary documents (*. suo), yet we devote the.user documents. The.user documents has as an example the start alternatives for debugging the task. You can locate the start alternatives in the buildings of the task in the tab "Debug". We made use of NUnit in some tasks and also set up the nunit - gui.exe as the start alternative for the task. Without the.user documents, each employee would certainly need to configure it independently.

Hope this aids.

2022-06-25 03:12:45

They have the details setups concerning the task that are commonly appointed to a solitary programmer (like, as an example, the beginning task and also beginning web page to start when you debug your application).

So it is much better not including them to version control, leaving VS recreate them to make sure that each programmer can have the details setups they desire.

2022-06-25 03:12:36

Using Rational ClearCase the solution is no. Just the.sln &. * proj needs to be signed up in resource code control.

I can not address for various other suppliers. If I remember appropriately, these documents are "user" details alternatives, your setting.

2022-06-25 03:12:34