Re: Polymorphism & Collections

I have a quick question about your implementation.

Doesn't this violate n-tier design because the datalayer has knowledge
of the business layer objects? I thought the data layer was only
supposed to return records (DataReader) in this instance, or is all of
this code in your data layer?

From other NG postings, I've had people tell me that the Data Layer has
NO knowledge of business layer objects, doing so violates proper N-Tier
design and tighly couples your business layer with your data layer.

.

Relevant Pages

  • Re: Circular Referencing in C#
    ... A classic three-tiered design. ... business layer, never to the data layer. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Circular Referencing in C#
    ... > business layer, never to the data layer. ... three main frameworks that provide all the services necessary for completely ...
    (microsoft.public.dotnet.languages.csharp)
  • Same Old ObjectDataSource Problem
    ... the data layer, one for the business layer and one for the ... simple one on which I have an ObjectDataSource and Gridview to display ... but then the ObjectDataSource still invokes its ...
    (microsoft.public.dotnet.framework.aspnet)
  • LINQ- Compiled queries and data layers
    ... before LINQ we all used stored procedures ... We also used to have wrappers for stored procs in the data layer (now LINQ ... Opinions on the little business layer and data layer methods below ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Data Layer Relationships
    ... I dont even think you should crank out a business layer for AD that ... ActiveDirectoryDomain or from ActiveDirectoryGroup. ... Data Layer classes? ...
    (comp.object)