locked
Need Best folder structure for multiple web project solution RRS feed

  • Question

  • User404854294 posted

    Hi,


    currently  i have a web application in ASP.NET 1.1 and need to re write in ASP.NET 4.0. the current folder structure is something like this.

    http://yfrog.com/5jmyprojectstructurep

    Now i am working on new project structure. i am looking for some inputs, is this structure is OK ?

    i would like make it more organized way. as this project is developed in 1.1 we didnt taken care of N-Tier architecture. so the Business Layer and DAL are scattered all over the project where it is required.


    and also i have another requirement that, now the users will be created for module level. it should accessable like

    www.mydomain.com/Module1 (after login). to achive this i am thinking to split the modules into different web projects. If i do so then again i have the confusion that do i need to have BL & DAL for each web project for each module or not.


    please give your inputs

    Thanks

    Monday, January 25, 2010 5:43 AM

Answers

  • User-952121411 posted

    http://yfrog.com/5jmyprojectstructurep

    Now i am working on new project structure. i am looking for some inputs, is this structure is OK ?

     

    There does not seem to be any problem with that structure (except the names are not too readable, but you probably just gave a quick example).  Some people like to group pages by their type.  For example mysite.com/Admin/Security.aspx  or mysite.com/Pages/DataEntry.aspx etc.  This is not required, but can be a nice way to organize the site structure.

    i would like make it more organized way. as this project is developed in 1.1 we didn't taken care of N-Tier architecture. so the Business Layer and DAL are scattered all over the project where it is required.

    Do not confuse anything about physical site structure and the associated URLs with n-tier development.  The BLL and DAL are really behind the scenes from the UI and have nothing to do with page URL structure.  N-tier development is an architecture to divide application responsibilities logically into separate layers.  You may want to look at the following thread for some good reading on n-tier development:

    http://forums.asp.net/p/1511760/3611556.aspx#3611556

    www.mydomain.com/Module1 (after login). to achieve this i am thinking to split the modules into different web projects. If i do so then again i have the confusion that do i need to have BL & DAL for each web project for each module or not.

    It just depends; the application could potentially use the same BLL or DAL if the UI portions all need the same functionality.  If they really are completely different web applications, then you will probably need to build that structure for each application.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, January 26, 2010 11:54 AM