We have a Windows Forms application using LLBLGen 2.5 with SQL Server.
We chose the SelfServicing model, and make heavy use of the Entity, Collection and TypedView classes, including some custom code regions. Some of our business logic lives within the LLBLGen classes.
The one downside to this approach is that the Windows application communicates directly with SQL Server. Firewalls get in the way, and security becomes a concern.
We would like to re-architect the application so that the client does not connect directly to SQL; it should connect to an application layer via HTTP or HTTPS, i.e. via .NET Remoting or Web Services. And, we want to do it as easily as possible without having to rewrite a lot of code.
I realize it might have been easier had we chosen to use Adapter; then plugging in remoting or WCF might be straightforward. But we want to continue to use SelfServicing if possible, to avoid rewriting practically all of our data access code.
Is this a losing battle, or are there effective ways to introduce a middle tier using SelfServicing in LLBLGen 2.5?