I would use patterns like Façade, Mediator or Dependency Injection and
design methodologies like interface-driven-design to attempt to abstract
customer-specific functionality into decoupled classes or even assemblies.
One solution is to rebuild your solution into a specific binary per
customer.
from a "managing source code, customer versions & release management"
perspective, i'd suggest the following model.
Have a "core" codeline that holds everything that is common across all
customers.
Branch it once for each customer.
as you change the "core" code, merge is across to each customer b
Yes, I agree.
Having multiple cores for an application will only lead to a great many
nightmares.
On 9/5/07, Bob Provencher <[EMAIL PROTECTED]> wrote:
>
> That's a common problem. Abstract out the customizations into handlers,
> interfaces, etc so there is only one core.
>
> -Original Messag
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-DOTN
