That's a common problem. Abstract out the customizations into handlers, interfaces, etc so there is only one core.
-----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Paul Cowan Sent: Wednesday, September 05, 2007 10:45 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: [ADVANCED-DOTNET] code stream versions Hi, We are running into an increasing problem with our product which I could really do with some advice from someone of an experienced nature who has possibly come across this problem before. The problem is this: We have a core product that 10 customers have bought. The problem is, each one of these customers has made changes that customise the product to their own need and has required meant that we have 10 branches of the code. As we get more customers then this will mean more branches of the code. Can anyone give me any advice of what is good practice for this type of problem? Thanks Paul [EMAIL PROTECTED] _________________________________________________________________ 100’s of Music vouchers to be won with MSN Music https://www.musicmashup.co.uk =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
