Versioning question

  • Thread starter Thread starter Mvk
  • Start date Start date
M

Mvk

Hi;

I have 2 projects here at work. A dot net 1.0 project and a dot net 1.1
project. The are ALMOST the same. Except that the 1.0 project is using COM
objects and the 1.1 project .NET object. They are a little bit different in
usage. So the projects aren't exactly the same.
The problem is that when I change something in the 1.0 project I also have
make the same changes in the 1.1 project. This is a very time consuming
job. So I am wondering if there is a way to koop both projects up to date as
easy as possible.

Regards
Marten
 
I use SourceSafe, and in this situation a have 3 projects: Common, Proj1.0 & Proj1.1 . In Common, I put the 'common' code (maths, utils, business rules, ..). I then SHARE the Common code into projects Proj1.0 & Proj1.1. Thus ONE copy of a module in SourceSafe becomes THREE local copies on my hard drive. I can edit ANY of the three local versions, and (so long as I check it in & do a 'get latest' for all projects) all my projects are current

Should one project need, say, a special DotNet1.1 feature, I create (say) a Common2 project and start 'migrating by osmosis' - Proj1.1 uses some source from Common & some from Common2. Alternatively, do a branch in creating Common2, but then you have the same problems as you do now (unless you have a CommonCommon being used in .... !

Remember to label your builds, so you know how to go 'backwards' in time.

Hope that helps
 
Back
Top