ScottW School of Rocking Web Apps, Part I
I am currently a serious student of the Scott Watermasysk School of Rocking Web Application Design. I am working with his .TEXT framework and customizing it to meet specific needs of my company. (More on that when the customization is complete.) But as someone said before me, studying Scott's code is an excellent lesson in Best Practices. I heartily agree.
|One of the things that struck me was how Scott breaks out the application to multiple project classes. I was thinking about how to keep my web application .DLL from becoming too large (I personally don't like to exceed 200K in a web app's DLL.) While engaged in this thought process I look at Scotts project layout in VS.NET (at right.) I've seen this before when I studied the Angry Coder's eZine framework, heck, a year-and-a-half ago, but the light didn't turn on like it did when I looked at the .Text solution window. I would in the past have a /components subdirectory and try to adhere to putting my business and data layers there, but breaking out the various components into separate project classes (and thus DLLs) seems to be exactly where I want to be going in my web app design.
It is also quite cool that VS.NET handles the references and compilation of the classes which comprise the solution. I used to think the references had to be deleted and re-referenced each time the project referenced was changed. Wrong!
Its the first time I say this and I'm sure it will not be the last time: "THANKS, SCOTT!"