Perforce (and other version control) best practices

[InfectedFPS]

@Neverender;15139

I found this entry on AnswerHub where someone from Epic recommends against committing the solution or project files to version control. Does that mean every developer individually re-binds to source control in Visual Studio each time those files are regenerated? Also, although it’s not mentioned, I assume it’s best to exclude the DerivedDataCache directory.

I ran into this issue when originally setting up my project for source control. After talking with Noland and some browsing on the AnswerHub I found why they recommend this.

Here’s all I store in my repository for a UE4 project.

So when we pull the proejct we go to the folder where it’s stored locally, right click on the .uproject, and click “Generate Visual Studio Files”

.gitignore

Binaries/
DerivedDataCache/
Intermediate/
Saved/

*.filters
*.opensdf
*.sdf
*.sln
*.suo
*.user
*.vcxproj