What does your ASP.NET architecture look like?

Results 1 to 2 of 2

Thread: What does your ASP.NET architecture look like?

  1. #1
    Join Date
    Dec 1969

    Default What does your ASP.NET architecture look like?

    &nbsp;<BR>Hi,<BR><BR>What are you folks doing out there as far as physical architecture? and what did you find works well and what to avoid?<BR><BR>We&#039;re in the process of designing a site using MS platform and ASP.NET.. etc., but wanted to get your thoughts on what components are sitting where (jpgs, asp, config.. etc.). Is the web and app layer on the same layer/different... any thoughts and recommendations are appreciated.. even pointers to case studies or white papers... <BR><BR>Thanks in advace..<BR><BR>Shami

  2. #2
    Join Date
    Dec 1969

    Default RE: What does your ASP.NET architecture look like?

    I HIGHLY.. recommend using stored procedures for anything database related. Not just for speed but for modularity and database integrity. Build your database as a seperate component and then build your app on top of your database. Sql statements inside your code tends to get messy in the long run.<BR><BR>Use codebehind. Or inherits or whatever you want to call it. It makes the understanding of code reuse better and allows you to keep your code proprietary. <BR><BR>Make a global namespace. Like the name of your company or something.. Put any classes you think that can be reused inside there. And if possible register it in the GAC. And if you have need to port an app to another machine you can just upload it to the bin directory.<BR><BR>Comment your code before its too late.<BR><BR>Think of everything you can and you think you will need from your database first. Very important. Of course you cant think of everything. But the more complete the better. The application relies heavily on the database. <BR><BR>as far as folder structure goes. Just keep everything organized. If a folder is getting large then you should be able to break it up into subfolders. Keep a global images folder for images that are common. if your images folder gets to large then you can make an images folder in the subfolder that the page is in. Make use of user controls for headers footers and commonly reusable components. For instance.. I just made a control that contains a next.. back button and a page jump for paging. It takes a totalpages parameter and thats all. Its reusable for any page that needs paging. And if I need to change the design of it it will reflect all pages. <BR><BR>Make use of the wonderful caching capabilites of asp.net. <BR><BR>Other then that. Just keep things organized and commented. Make global documentation. <BR><BR>---------------------------------------<BR>Codewarrior wished he practiced what he preached.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts