architecture - What is the best folder stucture in TFS for reporting service projects -
i'm looking on deciding useful folder stucture strategy reporting service projects in tfs. 1 have suggestions on way should stucture tfs? should project per report or should 1 reporting project multiple folders under main contain report projects?
i.e. senario 1 (separate projects each report project)
$reportproject1
$reportproject2
$reportproject3
senario 2 (main report project in tfs , subfolders report projects)
$reportingservices
------src
---------project1
-----------reportproject1 files
---------project2
-----------reportproject2 files
---------project3
-----------reportproject3 files
i lean towards fewer team projects, better. reports fall logical "packages"? have absolute need manage them separately? flexible enough work single project on multiple projects?
when scoping team projects - regardless of type of solutions stored within them - try come best balance between granularity , deployability. remember, if going set work item tracking, team builds, or going use project portals - each team project becomes delineation between them.
for things wit, can provide separation through functional areas. builds, going have 1 per project if plan on keeping simple , straightforward. portals not selling point 1 way or other in final determination me, although ad security groups map team projects makes little more important.
without knowing details of situation, still lean towards "scenario 2". having switch between team projects , know 1 few keystrokes/clicks more want have on ongoing basis. if wanted branch couple of reports, branch more needed maintain multiple branches.
Comments
Post a Comment