We create a single project for those and then use an Area classification to differentiate between the work items.
Wes Wes MacDonald LIKE 10 INC.<http://www.like10.ca/> 1150 - 45 O'Connor Street Ottawa, ON K1P 1A4 Microsoft MVP: Visual Developer - Team System<https://mvp.support.microsoft.com/profile/Wes.MacDonald> | Blog<http://wesmacdonald.spaces.live.com/> | Mobile: 613.219.7841 | Office: 613.755.4055 | MSN<mailto:[email protected]> "Risk comes from not knowing what you're doing. " -- Warren Buffet ________________________________ From: [email protected] [[email protected]] On Behalf Of Alastair Waddell [[email protected]] Sent: Sunday, October 18, 2009 9:35 PM To: ozTFS Subject: TFS Practices Hey All, Just looking for other peoples ideas as to how you structure you projects… If you have some small applications that don’t really fit the requirements for a full blown project then do you just create a “Stuff I need in Source Control” project and add the source code for each of these applications, or do you create a project for each of these applications Eg I have created some installer projects for installing the Reporting Services Printer client (2005 and 2008) and these don’t really have the need for bug tracking etc…but do want then under source control Alastair
_______________________________________________ oztfs mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/oztfs
