# What files should go in source control

**URL:** https://www.finalbuilder.com/forums/t/what-files-should-go-in-source-control/494
**Category:** Discussion
**Created:** [June 15, 2007, 2:48am UTC](https://www.finalbuilder.com/forums/t/what-files-should-go-in-source-control/494 "2007-06-15T02:48:08Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![tate](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/t/e19b73/32.png) [@tate](https://www.finalbuilder.com/forums/u/tate)
#### Post date: [June 15, 2007, 2:48am UTC](https://www.finalbuilder.com/forums/t/what-files-should-go-in-source-control/494/1 "2007-06-15T02:48:08Z")

</div>

Interesting blog entry by Chris May on the subject.

[http://www.chrismay.org/2007/06/14/What+Files+Shoud+Go+In+Source+Control.aspx](http://www.chrismay.org/2007/06/14/What+Files+Shoud+Go+In+Source+Control.aspx)

&nbsp;

Chris links to a Microsoft document: [Explained: Structuring Your Solutions and Projects in   
Source Control with Team Foundation Server](http://www.codeplex.com/VSTSGuidance/Project/FileDownload.aspx?DownloadId=9466)

Summary:

This article explains how you can structure Visual Studio solutions and projects in Team Foundation Server Source Control as well as on your local computer's file-system. The client and server-side folder structures and conventions discussed in this article are not the only approach you can adopt, but they represent an approach proven to work effectively for many team development scenarios working on a variety of different application types.

&nbsp;