Hi
Have joined a company newly and the team has developed one application in ASP.NET planned for one entity.
Now this application has been rolled out to 5 other group entities and our team have created 5 databases, and 5 copies of the source for all these entities. There are difference in some of the features.
Currently we make changes in one code base , do the build and realease /deployment.
Now we are planning to use TFS. We have the trial version of TFS.
My question is how do I structure my code in Source Safe.
1) We want to have one code base with options to have specific exclusive code(feature) for some entities.
2) We must be able to develop new features and release it to say Company A, Company C and Company D.
3) We must be able to make a build and deploy the same with very less effort.
4) Any Bug fixed must be one time fix across entities.
Example
Company A may have feature 1,2,3,4
Company B may have 1,2,4,5
Company C may have 1,2,3,7
Added to this there is virtually no documentation available. Every thing is in the Head ;) / Human memory.
Would Appreciate if some one has encountered the same problem and resolved it.
I was directed to this discussion fourm.
I guess some one would have solved this problem using branching.
Would Appreciate some help / suggestion.
Best Regards
Vadhi
Have joined a company newly and the team has developed one application in ASP.NET planned for one entity.
Now this application has been rolled out to 5 other group entities and our team have created 5 databases, and 5 copies of the source for all these entities. There are difference in some of the features.
Currently we make changes in one code base , do the build and realease /deployment.
Now we are planning to use TFS. We have the trial version of TFS.
My question is how do I structure my code in Source Safe.
1) We want to have one code base with options to have specific exclusive code(feature) for some entities.
2) We must be able to develop new features and release it to say Company A, Company C and Company D.
3) We must be able to make a build and deploy the same with very less effort.
4) Any Bug fixed must be one time fix across entities.
Example
Company A may have feature 1,2,3,4
Company B may have 1,2,4,5
Company C may have 1,2,3,7
Added to this there is virtually no documentation available. Every thing is in the Head ;) / Human memory.
Would Appreciate if some one has encountered the same problem and resolved it.
I was directed to this discussion fourm.
I guess some one would have solved this problem using branching.
Would Appreciate some help / suggestion.
Best Regards
Vadhi