Forum Moderators: open
I've got a bit of a common question here. Basically, I'm on the verge of developing a fairly hefty web application, and I'm wondering how to structure the project, particularly in terms of the number of projects involved.
I've done it two ways - I've got some applications that are just a single application, containing different layers, classes, etc, and I've also got some applications that I've broken down into a number of smaller projects, that are referenced by the main, master project.
My preference is definitely the latter, because I can maintain each individual project on it's own, without having to crank up the entire project and maintain that.
I'm just wondering - are there any performance issues with referencing projects as apposed to keeping all code within a single project? I have to admit...my understanding of the behind-the-scenes of .NET is limited to say the best, so any advice would be appreciated!
Just for reference, I'm on ASP.NET 2, and I'm talking of having up to 20 (ish) sub-projects within the application.
Any suggestions?
Cheers!
B
A separate Class Library for each of the following:
- Data Access Layer
- Business Logic Layer
- Entity Layer
(Seperating different functionality by way of namespaces)
Also a class library containing useful tools and functions, such as:
- Base Page class
- Application Settings and Session info Class
- etc. etc.
I then create the Web Site or Web Application which references all of these Projects (or Assemblies, whatever you prefer)
I'm a big fan of Imar Spaanjaars work, here is a great tutorial on N-Layered Web Applications with ASP.NET 3.5:
[imar.spaanjaars.com...]
