Debugging Tools And Fun, Erm...

Some useful links if you're trying to find web dev debug tools:

• TinyGet, for automated page requests: http://code.google.com/p/toolsdotnet/wiki/TinyGet
• WFetch (like TinyGet but with a GUI): http://support.microsoft.com/kb/284285
• The IIS6 resource toolkit: http://support.microsoft.com/kb/840671 (contains tinyGet & WFetch)
• A handy link on StackOverflow which should provide inspiration: http://stackoverflow.com/questions/1369829/how-to-debug-an-asp-net-applicaiton-on-live-server

Of course, deploying your DLLs in debug mode can help your logging, but release mode is going to provide at least 4x performance improvements. If you attach a profiler for checking memory usage or performance, you can leave your .pdb files up to get more information as these contain the .NET symbols used for inspecting the code. Please don't leave them there, as they are a serious security consideration - in short, if a hacker were to copy your pdb files from your server they've effectively stolen everything but the source code:

• http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/08/22/how-many-secrets-do-net-pdb-files-really-contain.aspx

Here's some profilers that don't involve installing Visual Studio on a live server (always a bad idea):

• DotTrace (won't memory profile .NET1.1): http://www.jetbrains.com/profiler/index.html
• Red-Gate Developer Bundle (plus separate downloads): http://www.red-gate.com/products/dotnet_tools_overview.htm
• Red-Gate's SQL bundle: http://www.red-gate.com/products/sql_bundles/SQL_Comparison_Bundle.htm
• DynaTrace (I've not checked this out yet): http://www.dynatrace.com/en/
• Ipcas SpeedTrace (or this): http://www.ipcas.com/trace-and-profile/c-sharp-and-vb.net-tracer-and-profiler/

There are, of course, sites out there for providing information about your site:

• Repeatedly tests your site: http://www.siteconfidence.co.uk/
• Multi-browser testing: http://www.browsera.com/ via: http://lifehacker.com/5414998/browsera-simultaneously-tests-your-site-in-different-browsers
• Installed on your network, provides processor information: http://www.zabbix.com/

Of course, if you're intent on debugging in Firefox (www.firefox.com, of course) you should have:

• Firebug: https://addons.mozilla.org/en-US/firefox/addon/1843
• Firebug javascript debugging: http://getfirebug.com/js.html

Some tools for developing your code (essentially, my favourites, as there are tonnes, Microsoft's list notwithstanding (http://msdn.microsoft.com/en-us/magazine/cc300497.aspx)):

• Beyond Compare, the best comparison tool anywhere: http://www.scootersoftware.com/
• SVN or CVS
• ViewState decoder: http://alt.pluralsight.com/tools.aspx

And a list of developer must-have's:

• http://stackoverflow.com/questions/180939/net-must-have-development-tools

And finally, a handy selection from youtube:

• http://www.youtube.com/results?search_query=debugging+.net&search_type=&aq=f

And once you've done all that, make sure it's performant:

• http://msdn.microsoft.com/en-us/library/ms998549.aspx