Architecture of my ASP.NET app

I'd appreciate some help from any architectural gurus out there. I'm creating a web app with 3 tiers,


A presentation layer which is an aspnet application.

A business object layer which is a group of custom classes that map to my database entities, items of each type, for example 'clientitem' and collection classes that are collections of items, for example 'clientcollection'.

A data access layer that uses a component class connected to a sql database and uses commands, adapters and datasets to return my data to the business object layer.


I've referenced the bol in my aspnet app and get some quite useful abstraction from the database using this method, my aspnet app is completely ignorant of any information regarding the database, field names, anything really.

I've referenced my dal app in my bol app and what I am finding is that I am now required to tie the business object layer to the database layer, field names etc, I could use field position numbers/ordingals but I find this unreliable, confusing and possibly troublesome, I don't want to tie my bol to my dal, how can I avoid this? Or am I just dreaming, I realise the rubber has got to touch the road somewhere, the only thing I can think of is referencing back to my bol app from my dal app(this would allow me to return native bol app entities) but that sort of negates having seperate apps for them in the first place.

Basically I'm returning datasets or results as parameters from the dal to the bol, then map them into the bol apps entities, how would you guys achive this with some level of abstraction....?

regards,
JCC.
User submitted from AEWNET (http://www.aewnet.com/)
.

Relevant Pages

  • Re: OODesign - OPF, design pattern
    ... I wanted to put across that an app layer is ... if you hadn't used the framework in the first place. ... the plugins to be managed or unmanaged. ...
    (borland.public.delphi.non-technical)
  • Re: Data Limitations
    ... My database layer is getting a major upgrade due to .Net capabilities. ... App for HIPAA reporting and everyone needed the same data shown a different ... also needed to resuse this logic for a client side desktop app. ... making another trip to the db wasn't an option. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: OODesign - OPF, design pattern
    ... I developed a Pocket PC app last year using the compact framework. ... Maybe my design is just very simple then, ... and its in the application layer not the business ...
    (borland.public.delphi.non-technical)
  • Re: RT patch acceptance
    ... IO scheduler and the SCSI layer so that GRIO can happen. ... This is not trivial for dual kernel set ups. ... about how large X11 and running a task like that in a nanokernel ... easier than retargetting your app and layer to a nanokernel. ...
    (Linux-Kernel)
  • Re: DataSet Question -- Simple Concept? Beginner to 3-Tier asp.net
    ... information back and forth to that layer and let it do all the work. ... datasets with tableadapters that are now "disconnected" but most decidedly ... I am trying to be a thorough coder and create an app in layers. ... create a stored procedure ReturnProductsOverOneDollar. ...
    (microsoft.public.dotnet.framework.adonet)