CODEWITHSUNDEEP
c#visual-studio-2013perforce
Blankdud
Blankdud

Reputation: 698

What files to exclude when setting up VS2013 project and perforce

A few friends and I are starting work on an independent project. We will be using VS2013 and perforce to share version-ed files. Are there any particular folders/files that should be excluded from the depot? I have heard several different reasons for several different files, but I cannot find any specific mentions.

The most common thing I've heard is to exclude the bin and obj folders, and the .csporj.user file. If anyone can confirm or give me additional information, I would appreciate it.

Upvotes: 0

Views: 174

Answers (1)

hschne
hschne

Reputation: 704

As already mentioned, bin and obj should be excluded, the reason being that they contain products of the compiler, which need not be shared.

As other people have already pointed out, user specific information should also be excluded from any kind of versioning. User specific settings need not be shared. Examples for user specific files in Visual Studio are the .suo and .user files.

If you plan on using any add-ins (such as Resharper) or nugget (which I highly recommend) do not forget to exclude any folders and files introduced by those - for example, the packages folder.

Those should be the most important ones.

For a pretty detailed list of files which you could possibly want to ignore please check out this .gitignore file. But do keep in mind: Most of those ignores will not apply to your specific situation.

Upvotes: 2

Related Questions