Hello everyone,

This is a general high level type of question.

I want to use LLBLGen v2.5 along with a slew of partial classes to basically be my business logic and data tier. I've been playing around with the SelfServicing mode and so far having success with it.

Now for the going forward issue:

I'm in a typical business environment (internal network).

What I want to do is make this framework with LLBLGen and then distribute it to my UI designers so they don't have to worry about all this background stuff.

Should I keep doing what I'm doing and just distribute this DLL using the typical click-once (or loadfrom URL) methods? I'm currently loading pluggable modules at runtime via a load from URL method and it is working well.

or

Should I go the complex route and use Adapter with WCF? I'm not too sure about the gains to be made under the "complex" route.

Thanks, -Luke

Is the application going to be a distributed application?

Im a bit confused. It sounds to me like adapter maybe better suited for you. And i wouldnt screw with WCF in your case, if your .NET to .NET remoting is easier, at least last time i looked into WCF.

Answer wrote:

Is the application going to be a distributed application?

Im a bit confused. It sounds to me like adapter maybe better suited for you. And i wouldnt screw with WCF in your case, if your .NET to .NET remoting is easier, at least last time i looked into WCF.

I guess it is sort of distributed meaning that I have a main "shell" which can load one or more modules (DLLs) with a prescribed interface over the network. Imagine a click-once application which gets updated a few times a week.

This LLBLGen/Business tier can be a DLL which gets auto-updated on the client whenever I update that tier. That way the UI designers has full access for data-binding, special classes I add, and intellisense.

Given that scenario what do I get with adapter?

Would you allow the UI designers or developers to directly access the database without using your BL?

If the answer is no, then you shouldn't use SelfServicing, as a SelfServicing entity has it's save, delete....methods (persistence info is stored within the entity).

While the adapter entities know nothing about the database, they depend on the DataAccessAdapter to interact with the database.

That makes sense so... in the case of using a BL that does get distributed then it would be prudent to go with adapter. Thanks.

Walaa wrote:

Would you allow the UI designers or developers to directly access the database without using your BL?

If the answer is no, then you shouldn't use SelfServicing, as a SelfServicing entity has it's save, delete....methods (persistence info is stored within the entity).

While the adapter entities know nothing about the database, they depend on the DataAccessAdapter to interact with the database.