Visual Studio and Windbg: which one is better to debug a large-scale managed application

Visual Studio seems very native to debugging a C # project, but when the scale is up, it seems not very convenient to debug, for example, when the project contains some code that calls / outputs from native code ...

I want to know if there is any evidence that windbg is better than VS.Net when we are debugging a large / serious project.

Another question: without the SOS extension, can windbg set a breakpoint on the C # source file?

+2
source share
3 answers
  • WinDbg is at least an order of magnitude faster than VS when debugging unmanaged applications.
  • ; , VS.
  • WinDbg SOS.

, VS WinDbg. :

  • . .
  • WinDbg .
  • VS WinDbg.
+5

hanselminutes podcast windbg:

, - ASP.NET . .NET Debugging 101. ? PDB? WinDBG , .

+3

WinDbg . , , , .. . VS, WinDbg .

WinDbg - , , , , WinDbg , VS . , .

WinDbg + SOS . 6.7.5. . : http://voneinem-windbg.blogspot.com/2007/04/windbg-6750-released.html

SOS ( .NET 4) , ( ! u).

+2

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


All Articles