ASP.NET Life Cycle and Best Practices - The Config File

(Page 5 of 5 )

1. Avoid making changes to pages or assemblies that are there in the bin directory of the application. A changed page will only recompile the page. Any change to the bin directory will result in recompile of the entire application.
   
   
2. The config file is configured to enable the widest set of features. For a performance boost it is better to tune it to the requirements. Some key points here are:
   
   • Encoding - Request/Response - The default is UTF-8 encoding. If the site is completely ASCII, change the option to ASCII encoder.
     
     
   • Session State - By default is ON. If session state is not maintained then the value should be changed to OFF.
     
     
   • ViewState - Default is ON. Turn it off if not being used. If ViewState is being used there are different levels of security that need to considered which can impact the performance of the application.
     
     
   • AutoEventWireup - Turning off AutoEventWireup means that the page will not try and match up method names to events and hook them up (i.e. Page_Load, etc).  Instead, if the application writer wishes to receive them, they need to override the methods in the base class (i.e. override OnLoad for the page load event instead of using a Page_Load method).  By doing so, the page will get a slight performance boost by not having to do the extra work itself, but leaving it to the page author.
     
     
3. For efficient debugging Use ASP.NET trace feature to debug instead of Response.Write.

Conclusion

Performance is the main objective for most of the ASP.NET applications. Each time we request an ASP.NET page, we run through the same process from initialization to disposal. By understanding the inner workings of the ASP.NET page process and following the above mentioned tips, writing and debugging our code will be much easier and effective (not to mention less frustrating).

DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

Comments On: ASP.NET Life Cycle and Best Practices

>>> Be the FIRST to comment on this article!