Good Day,
I'm going to attempt code re-use (CSLA BO's) across 3 applications and would appreciate some thoughts.
I have 1 Windows-based desktop application ( I will call it ABCWin ) and 2 Web-based applications ( I will call them DEFWeb and GHJWeb). They all use the exact same XYZPrincipal and XYZIdentity for security, which talks to a single security database on my SQL 2005 Database Server. I want to put this dll on an Application Server under IIS and ASP. CSLA is on the Application Server. For ABCWin BO's and CSLA is on Desktop as well.
I have shared functions across all 3 applications. I want to put this dll also on the Application Server.
I want to "pool" my BO's (their are a few BO's that is used amongst all applications) into their own dll's and put them on the Application Server.
The Application Server will have a web.config file which contains the info for talking to the Database Server and that supports .NET remoting.
ABCWin will talk to Application Server which talks to Database Server.
DEFWeb of which the website is on a Intranet Server will talk to the Application Server which talks to Database Server.
GHJWeb of which the website is on a Internet Server will also talk to the Application Server which talks to Database Server.
How does that sound?
Regards,
Sounds like a perfectly acceptable thing to do. You're taking the same business functionality and exposing different aspects of it across 3 different UIs.
Sounds like exactly the kind of requirement CSLA was designed to handle.
Copyright (c) Marimer LLC