TFS & Disk structure - folders vs solutions

May 22, 2010 at 1:56 AM
Edited May 24, 2010 at 4:43 PM

A lot of the guide seems to be geared toward adding new solutions to an existing structure.  What if we just built our solutions without TFS, and now we want to load them into TFS?

I have built the disk structure to following the general guides, except on thing that I didn't see.

For example, our .NET and BizTalk naming convention is something like this: CompanyName.AppName.AppFunction.BizTalk.Type.

I currently have the disk structured Under Project/Main/Source/CompanyName/ApplicationName/AppFunction.BizTalk/Type/CompanyName.ApplicationName.AppFunction.BizTalk.Artifacts.sln.

I remember having to following this type of pattern at some place I worked in the past. Is it advised to match the disk directory to your xx.xx.xx.xx naming convention of your projects? 

So when I check in - it looks like I have two options:  I could either do 1) "Add Folder" and pull in my whole "Project"Directory (with all children) at once,
or 2) I could open each solution and check it in. 

Thanks,

Neal Walters