Configuring Team Foundation Server 2010 branching

Question

We are creating a completely new TFS 2010 server without using TFS before (or, oddly enough, no other central source management system). Here, the general structure of our small team (of 6-7 programmers) spoke about customization, and I'm curious, based on the experience of others working with TFS, if this is a good idea or not (these names are simply descriptive, not what we plan to use ):

$/
    Our Organization Collection/
        .Net technology projects/
            class libraries projects/
                Project 1/
                Project 2/
                Project 3/
                etc.../
            ASP.NET projects/
                Project 1/
                Project 2/
                Project 3/
                etc.../
            Windows Workflow Foundation projects/
                etc.../
            WPF projects/
                etc.../
        Other non .NET source code/
        SQL/
        Server configuration/

(etc.)

Will we regret this structure after a year of use? The application will cover many parts of this structure - will this be a problem for management?

At what level do we configure release / main / dev branches?

Thanks for any input and guidance!

Answer 1

. .

, /, , ( , ). VSS TFS2010 " " , :

, . , . TFS , , .

, , , , . , , ; , , DOCUMENT ; , . , , , .

, . , .

---

:

, , , , . - , /. , TFS / .

Team Project . Team Project - , . . :

. ( / ). .

, . - ?

Answer 2

@hangy, TFS 2010 , codeplex Visual Studio TFS 2010 .