Building a Best Practices Analysis Tool for Asp.Net deployment
Hello all,
I am gathering Rules/Best Practices recommended when developing ASP.NET applications and services. The intention is that we will ship a tool (Power Toy) that performs the analysis on your web sites that you could also extend to include new rules. Whether gained through personal experience or learned formally, I would love to hear your suggestions for default rules.
Context
The context to which I’m speaking of is with the .config files (machine.config and web.config) associated with ASP.NET projects. i.e what settings should and should not be made in said files.
Examples
EnableSessionState = false. Set in web.config for all pages that don’t utilize session data. Enable only when necessary.
AutoEventWireup = false
Suggestions in all areas, not limited to the following, are welcome.
- Performance
- Security
- Presentation
Thanks
-Ifeanyi Okpareke (After Market Solutions Team)
Comments
- Anonymous
June 05, 2006
Search strings and find html tags in strings. I would think that it would be best to create a control object, and to then render the control into a string to prevent breaking the capatability layer. - Anonymous
May 29, 2009
PingBack from http://paidsurveyshub.info/story.php?title=dde-team-blog-building-a-best-practices-analysis-tool-for-asp-net