Version Control Managment

  • Thread starter Thread starter romy
  • Start date Start date
R

romy

Hi,

I would Like your Options on complex version Control Management methodology.

Typaclly We Have three enviroments: Development, Test and Production..
After SourceCode is checked carefully in the Develompent enviroment, it is
copied to Test and then to Production. All is fine and well known.

Our Problelm Starts when for example some of the models is due to production
A week from now (Group A) and some two monthes from now (Group B).
Group B models Shares code with Group A (For Example ASP Forms), However
uses a newer code which should not compiled to production in the next week.

So it happens Some Group B code were compiled to producution even though we
didn't want to.

ofcourse our tools in hand is Visual SourceSafe.

thanks
 
romy said:
Hi,

I would Like your Options on complex version Control Management
methodology.

Typaclly We Have three enviroments: Development, Test and Production..
After SourceCode is checked carefully in the Develompent enviroment,
it is copied to Test and then to Production. All is fine and well
known.

Our Problelm Starts when for example some of the models is due to
production A week from now (Group A) and some two monthes from now
(Group B). Group B models Shares code with Group A (For Example ASP
Forms), However uses a newer code which should not compiled to
production in the next week.

So it happens Some Group B code were compiled to producution even
though we didn't want to.
Click to expand...

don't share files between projects, share projects between solutions.
So if you have 2 projects, A and B, and A has a file which can also be
used by B, you can't share it, you have to create a subproject and
share that among the two projects.

This is because the compilation result is a single entity, e.g
assembly.

With webforms it LOOKS like this is different, but it's not, webforms
have code which rely on other pieces of code, so changing that code
will then cause problems if you share that page among two different
projects.
ofcourse our tools in hand is Visual SourceSafe.
Click to expand...

Sourcesafe makes life harder than necessary. This is especially true
when you want to share projects among solutions as sourcesafe can't
handle that properly. Use subversion.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
Back
Top