All geek questions in one place

How to debug an application in a client environment.

We have an application written in C # .NET that is currently used in production environments. Obviously, the release build is being used.

Unfortunately, sometimes the application does not work correctly under certain conditions, and we cannot understand why. We cannot reproduce the problem in the house. Yes, more tracing will help, but often it happens after you realize that you need to track more.

What is the best way to debug this installation using regular, in turn, debugging of the Visual Studio Attach-to-Process type. Will the VS express version be installed on the client machine and replace the DLL with the debug version? Is it enough to just send PDBs and specific source files? Is there a better way? The ultimate goal is to create a development environment to debug the problem.

+3
source share
4 answers

- , , ( ), ( )

.

PDB . Clr Debugger (DbgCLR.exe). VS Debugger, , , .NET SDK. Clr Debugger, VS ( ). , 90- .

, , , - ( ) , .., , . Windows, , - .

, 50% "" .NET - (, , First Wins/Last Wins). , , VS ( ), 2 .

, , . .

+7

-, , PDB ( PDB ). , Visual Studio , . PDB , , - .

+2

, , .

0

I suggest you use the exception libraries from the Enterprise Library. Using this, you can write your error messages to your email / database / text files, etc. So that you can accurately understand the cause of the error.

http://www.codeproject.com/KB/aspnet/ExceptionHandling.aspx

0
source

Source: https://habr.com/ru/post/1712468/

More articles:


All Articles