Databases
StackOverflow2013
Postsdbo
POProject Structure for N-Tier Architecture in .Net - Cross Referencing Layers
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POProject Structure for N-Tier Architecture in .Net - Cross Referencing Layers
    primarykey
    data
    text
    <p>I'm implementing an N-Tier architecture in .Net, comprised of an Entity layer, a DAL layer, a Business layer, and a UI layer.</p> <p>The entities, in addition to primitive fields, contain navigation properties. An example of this would be an Invoice entity, which has an InvoiceLines property, which should return all InvoiceLine entities associated with the parent Invoice entity.</p> <p>Owing to the fact that there is business logic which needs to be applied to these InvoiceLines once they have been retrieved from the persistence medium, and not wanting to duplicate code, the InvoiceLines property on the Invoice entity populates itself via a call to a GetInvoiceLinesByInvoiceID method within the business logic, which returns IEnumerable.</p> <p>My problem is this - I cannot separate out the layers into separate projects, since the Entities project depends on the Business project, and the Business project depends on the Entities project, thereby introducing a cross reference. I currently have all 3 layers (Entities, DAL and Business) living in the same project, which works fine, but means I cannot share just the Entities amongst other solutions.</p> <p>I appreciate that by cross-referencing layers in this way I'm violating some principle, but it's extremely convenient to have navigation properties populated on my Entities with business logic applied to them.</p> <p>Can anyone please suggest a better approach, or some way I can do this whilst keeping my layers in separate projects?</p> <p>Cheers</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USHoodlum
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POProject Structure for N-Tier Architecture in .Net - Cross Referencing Layers
      1. USDigitalNomad
      1. VTFavorite
    1. COFor clarity, I need to share just the Entities layer with a SQLCLR project - the whole "Layers" project containing Entities, DAL and Business contains a bunch of referenced assemblies unsupported by SQLCLR, so I can't just add the entire assembly.
      singulars
      1. POProject Structure for N-Tier Architecture in .Net - Cross Referencing Layers
      1. USHoodlum
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload