Tuesday, February 26, 2008

Best Practices to Improve ASP.Net Web Application Performance.

This article gives some important points to consider for the performance improvement in asp.net applications.

http://www.dotnetfunda.com/
articles/article45.aspx

Validate XSL Against XML

In this Article, Haissam Abdul Malak shows how to create a class library for validating a certain XSL file against an XML file. He examines the concept with the help of a series of steps with relevant source code and explanations. Finally, he describes how to test the class library which was created in the previous steps.

http://aspalliance.com/
1567_Validate_XSL_Against_XML.all

AJAX localization

This article discusses:
  • Globalization support in ASP.NET AJAX
  • Need for support in JavaScript
  • Assembly-based AJAX localization
  • File-based AJAX localization
http://msdn.microsoft.com/msdnmag/issues/
08/01/InternationalizingASPNETAJAX/#S3

Adding a Build Banner to ASP.NET Pages

This article explains, and provides fully functional code, for a plugin to the HTTP pipeline which will render such a 'development banner' to any ASPX page in the website in question.
The only requirement is to add the appropriate configuration to the Web.config file, and ensure the banner assembly is in the sites bin directory.

http://www.codeproject.com/kb/
aspnet/buildbanner.aspx

Top 10 Best Practices for Production ASP.NET Applications

In no particular order, here are the top ten things I've learned to pay attention to when dealing with production ASP.NET applications. Hopefully they will help you save you some time and headaches.

http://daptivate.com/archive/2008/02/12/
top-10-best-practices-for-production-asp-net-applications.aspx

ASP.NET Memory: If your application is in production… then why is debug=true

This is another article which has some information about the impact of leaving debug=true in the production environment.

http://blogs.msdn.com/tess/archive/
2006/04/13/575364.aspx

App_Offline.htm and working around the "IE Friendly Errors" feature

This article gives a way to overcome the "IE Friendly Errors" feature interfering with the actual message coming from the server when the content length is less than 512 bytes.


http://weblogs.asp.net/scottgu/archive
/2006/04/09/442332.aspx