One of the most difficult parts of ASP.Net 2.0 application creation is configuring your site correctly.  It’s easy enough to actually set the settings, but how do you know the settings are correct?  What are the best practices for ASP.Net site configuration, and how do you check that your site is following those practices?

 

Announcing the Best Practice Analyzer for ASP.Net!  It’s currently just an alpha preview version—a shell of the application we hope to turn it into, but it should give you an idea of what we are thinking about.  The tool scans the settings for your ASP.Net application from your machine.config, root web.config, and site web.config files and notifies you of any potential errors, warnings, or suggestions to make your site configuration better.

 

We only have a few rules right now in the engine—this release is mainly to get feedback from the community and see what you think of the tool, but also to start gathering rules from the community.  What best practice for ASP.Net configuration do you have to share?  Let us know by leaving a message in our forum!

 

Sharing is the name of the game for this tool—this tool will be part of the Power Toys for Visual Studio, and the libraries we are using to make this an ASP.Net 2.0 focused tool will be 100% Shared Source!

 

Download the installer for the tool here.

 

Let me know what you think, and send some good rules for ASP.Net configuration!