What is the "Best Practice" to catch errors in production environment

Hi,

I am curious that how enterprise level applications catch errors on
production environment. I thought of multiple options.

1) One can put the .pdb file in the same directory as the dll, but I am not
sure if one should put .pdb files on the production environment in release
mode.
2) To make a custom framework which dumps the current state of all the
objects which fall under exceptional stack trace functions.
3) Use some tool like "DebugDiag" for crash and memory analysis. Again I
don't think that on the production environment, enterprise applications
monitor memory leaks, crash or exception using these kind of tools. It could
be heavy to use these along with the running application.
4) Microsoft applications/OS generally shows "Send", "Don't Send" dialog
boxes on any non-recoverable error. Is there any prebuilt framework which
can be extended to achieve the same?

Could somebody help me to find out the best practice for solving this
problem.

Regards,
Rajat.


.

Loading