Large Web Solutions and sub division


i'm curious others here. moving on large web project (.net 2.0, vs 2005) vss tfs. in vss there lots of smaller web solutions were a part of the larger web solution. allowed dev open smaller solution small web project , work - in turn made responsiveness in debugging , rebuild better. of course, 'partial' web project needed core parts primary web project. sharing being used here. allowed immediate chages replicated sub-solution mast solution.

 

as bring tfs sharing not, of course, option. 1 option having in 1 master solution , working master solution can slow load , build. option branching main solution create sub-solutions , getting load , build performance requiring merges.

 

how have others handled this? there plans refactor these sub-solutions can stand alone rely on various (different each sub-solution) parts of primary web solution.

 

 

using 'partial' solutions should work same in tfs did in vss.  long you've built prerequisites, , relative paths stay same, 'partial' solution should able resolve references projects doesn't contain directly.

edit: http://www.codeplex.com/tfsguide/wiki/view.aspx?title=chapter%206%20-%20managing%20source%20control%20dependencies%20in%20visual%20studio%20team%20system&referringtitle=home


Archived Forums V  >  Team Foundation Server - Source and Version Control



Comments

Popular posts from this blog

Conditional formatting a graph vertical axis in SSRS 2012 charts

Register with Power BI failed

SQL server replication error Cannot find the dbo or user defined function........