诊断部署到生产环境C＃.NET的.NET代码中的问题

Question

I want to find out what methods or tools in general can be used diagnose issues in .NET code deployed to a production environment.

Thanks!

Update

The types of application on live: Web application, WCF application.

Answer 1

Depending on the type of issue I am looking at, I usually go down this list:

1. Custom logs (if any).
2. Event logs.
3. .NET, IIS and ASP.NET Performance Counters.
4. Add Soap tracing, System.Net tracing, System.Net.Sockets tracing.
5. WinDbg memory/crash dump analysis.

Answer 2

If your .NET project is deployed to the production environment it's rather hard to debug it.

The one way is to have some logging tools integrated into software (eg log4net ) and to analyse the log messages.

Answer 3

What kind of product your interested in? Desktop or Web?

Anyway in any case you need log all unusual actions in any project.

For web application I recomend to use ELMAH whitch can be accessed remotelly and you can review all error and information records in it. As data source here can be xml, db or plain text file.

For desktop applications you still need to log errors and it would be really helphul to post errors to the server via some kind of "Report Bug" form.

Answer 4

As a general idea, an administrative console implemented into the application can be used to query its internal state.

This can be as simple as a status page in a web application that queries if the database server can be pinged, or as extensive as a transparent pull-down console that supports your custom DSL . An example to the latter might be some games from which one can query or update the game's internal data (commands such as 'GET_OBJECT_PROPERTIES #objectId' or 'ADD_WEAPON_TO_PLAYER #playerNumber #weaponId', etc).