Layered architecture

[Guest]

Hi.

It is often maintained, that a layered architecture is something one should
consider in any nontrivial application (see e.g. Data Binding with Windows
Forms by Brian Noyces).

I have a VS2005 solution with 3 projects in it:
1. Adveita.UI - a WinForms executable for user interaction
2. Adveita.BLL - a library project for buisiness logic
3. Adveita.DAL - also a library project, for data access

In order to achieve a full decoupling between the UI and DAL layers, I find
myself writing wrapper classes in the BLL layer to present tables, columns
etc. to the UI layer. Also, I am writing a lot of code to bind controls like
text boxes to data and the like. I think, that the designer should be doing
this for me in most cases and I that I am perhaps doing something basically
wrong here. On the other hand, examples in books and downloadable samples
are rather simplistic and hardly tackle questions like these.

Can anyone comment on this, point out to me samples or articles addressing
these questions.

Regards,
Gudni

 

[Guest]

Data binding on windows forms shouldn't normally take more than 1 line of
code for forms. You should be creating binding sources on your form. Using /
Making object datasources for those in your projects, then using drag and
drop to setup the databinding by draging fields from the datasources window
to fields on your for.

Rocky Lhotka has designed a good business object framework and written
accompanying books for it (http://www.lhotka.net/). I also a writing a
business objects entry for my blog which I was going to follow up with a
databinding windows forms introduction. but they arent ready yet.

HTH

Ciaran O'Donnell
http://wannabedeveloper.spaces.live.com