Can we seperate the Bussiness Logic and User Interface?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm going to build a project which contain the business logic only, and it
should be device independent. And I'll have different program to build the
UI in for different platform using the same library of business logic.

I have created a solution to contain projects for different device (Windows
and SmartDevice), however, I cannot cretae a project for the business logic
which can be shared for different platform. It seems that VisualStudio does
not support the idea of seperating the Business Logic from UI, all project in
Visual Studio are device dependent.

May I know if there has any alternative that I can have a single source for
bussiness logic, and share the source for different platform?
 
James MA said:
I'm going to build a project which contain the business logic only, and it
should be device independent. And I'll have different program to build
the
UI in for different platform using the same library of business logic.

I have created a solution to contain projects for different device
(Windows
and SmartDevice), however, I cannot cretae a project for the business
logic
which can be shared for different platform. It seems that VisualStudio
does
not support the idea of seperating the Business Logic from UI, all project
in
Visual Studio are device dependent.

May I know if there has any alternative that I can have a single source
for
bussiness logic, and share the source for different platform?

You can, however, share source code files between projects. On a project go
to Add/Existing Item and look toggle the "Add" button to "Add as link".

David
 
Encapsulate your business logic into Class libraries and use those entites
in your presentation/UI tier. This way, the UI layer talks to the BO tier.
The BO tier talks to the data tier. The UI should never talk directly to
the data tier in this architecture. Of course, you can't just use the wizards
and follow the simple samples to build a robust, re-usable architecture.
You may want to look at Rocky Lhotka's books for Business Objects as one
example of what you can do.

Jim Wooley
http://devauthority.com/blogs/jwooley/default.aspx
 
Back
Top