N- Tier Architecture in ASP.NET 2.0

Hi ..

I have to create n-tier architecture for my new project with visual studio 2005, asp.net 2.0 and SQL 2005..

I had seen my sample applications for that but they all are using a single project and creates Business and DataAccess class in App_Code directory so i am confused whether to use differenct projects (say one for BAL , one for DAL ) or to merge them in the single project... Any idea on which approach is better for a long term project...

Thnx in Advance,
Aryan


Answer this question

N- Tier Architecture in ASP.NET 2.0

  • tianyuan

    To get the best performance and to help with issues of scalability you will also need to think about the levels of cohesion and coupling that exist in and between your components. Try to have loosely coupled and highly cohesive components wherever possible.

  • Vanscarbs

    Hi Marius Gheorghe n  Ajakeman,
     
    Thnx for reply ... :)

    Any idea about if i use different project for Each Layer then will i be able to use the advantages of App_Code directory ... i.e. dynamic compling , DataAccess Class using DataSet(.xsd) file ... which will be better to use ... This will be a Large scale project with all almost the features ...

    Thnx Again...
    Aryan



  • SamyLahur

    Hi,
    Go with different projects for business facade, ui and data access. When the project grows it will be A LOT easier to manage multiple projects than a single monolithic one.

    Cheers,
    Marius Gheorghe
    www.voidsoft.ro


  • N- Tier Architecture in ASP.NET 2.0