If you move your code to libraries, you will have accomplished the
separation without invoking BizTalk. You will then, at least generally, put
a facade layer to query the objects from the UI.
While it is not the only, or necessarily the best, implementation,
dofactory.com has a Framework you can download ($99 for the entire package)
that has a reference application with multiple tiers and proper use of
design patterns. It is worth a look to see how someone separates business
logic from UI. I personally would consider a slightly different data layer,
but it is something you can work with.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
|
*************************************************
[quoted text, click to view] <nsajus@yahoo.com> wrote in message
news:1589f97b-d893-468c-94cb-b2c9a700c04a@u10g2000prn.googlegroups.com...
> Hi,
>
> I would like to know what is required to create and run a .NET client/
> server application?
>
> I am assuming the following for running a .NET application :
>
> 1. Microsoft .NET Framework version 2.0
> 2. Microsoft Windows 2000 Professional (Service Pack 3 recommended)/
> Microsoft Windows 2000 Server (Service Pack 3 recommended)/ Microsoft
> Windows XP Professional/ and Microsoft Windows Server 2003 family.
> 3. Internet Information Server
>
> We need to separate the business logic from the presentation layer.
> Should we use a Biztalk server for that?
>
>
> For creating a .NET application (Vb.net application), what is
> required? Is it the below?
>
> 1.Microsoft .NET Framework Version 2.0 Redistributable Package
> 2. Visual Studio .NET 2005
>
>
> And how does one separate the business logic from the presentation
> layer - using framework libraries?
>
> Any help will be appreciated.
>
> Thanks,
> Ann
>