Locked History Actions

MyBlog/BlogEntry-2007-11-12

My current client assignment takes me to an automotive manufacturer OEM. Part of my role is to act as a technical liason to several of the vendors that are providing implementations of web sites/services for the OEM. Today I find myself reviewing the application architecture and design specifications for the implementation in the previous phases. Here are somethings that I ran across that I like:

  1. Clear separation of the UI, business rules and presistance layer by use of separate projects which compile into separate assemblies with a clear understanding of the dependencies between them. Is your web application doing this?
  2. Code/logging to handled uncaught exceptions in global.asax. Is your web application doing this?
  3. Use of satallite assemblies to deal with muliple languages. Is your application doing this? (See http://quickstarts.asp.net/QuickStartv20/aspnet/doc/localization/localization.aspx.)

  4. Encyrpt database connection strings in the web.config file. Doing this? (See http://msdn2.microsoft.com/en-US/library/ms998280.aspx for details.)


CategoryBestPractices