Create a third assembly that performs data access tasks and reference this
assembly from your Customer and Orders assemblies.
To get you started, I would recommend the Microsoft Data Access Application
Block, which is pretty good and easily integrated and extensible.
Dan
[quoted text, click to view] "JuanBarbatos" wrote:
> I am looking for some suggestion on the best way to handle this. I have
> broken my business logic down to 2 assemblies, Customer and Orders. Both of
> these will share the same logic for some general data bewteen the 2. For
> example Orders need to get address from Customer, and Customers may need to
> get Inventory totals from Orders.
>
> What is the best way to get this logic shared between these 2 assemblies? I
> want to keep code duplication to a minuimum.
>
I would put Customer and Orders in the same assembly. There's no reason to
have them in separate assemblies.
SP
[quoted text, click to view] "JuanBarbatos" <JuanBarbatos@discussions.microsoft.com> wrote in message
news:257D15D4-7F63-4654-A6DF-A85CFA18A995@microsoft.com...
>I am looking for some suggestion on the best way to handle this. I have
> broken my business logic down to 2 assemblies, Customer and Orders. Both
> of
> these will share the same logic for some general data bewteen the 2. For
> example Orders need to get address from Customer, and Customers may need
> to
> get Inventory totals from Orders.
>
> What is the best way to get this logic shared between these 2 assemblies?
> I
> want to keep code duplication to a minuimum.
>
> Any help would be greatly appreciated.