With the old .NET Framework, the excuse for why we could not have a public build of windbg with .NET source debugging was because of "proprietary undocumented interface blah blah". Now that .NET is open source, can we convince the debugging team to finally release an external build of windbg with .NET source level debugging?
This would be incredibly helpful for so many different development and troubleshooting scenarios. For example, when developing services, there are those times where you really need to debug service startup using the kernel debugger. In other scenarios, it is much easier to xcopy cdb or ntsd onto a target and then connect to it remotely without having to deal with the chaos of MSI installing some package on a target in order to do a live debug from a remote machine using "heavy" IDE tools. There are many valid situations where MSI installing such tools is unacceptable and/or undesirable.
To this day, the Debugging Tools are unmatched in their power in the right hands. It is a shame that only internal Microsoft folks can source level debug .NET code with them.
Spoken another way. SOS is unmatched when compared to debugging .NET code in IDEs. There is just no comparison! Yet only internal Microsoft folks can harness the power of SOS coupled with source level debugging.
Please open this up for the masses now that ,NET is open source.
With the old .NET Framework, the excuse for why we could not have a public build of windbg with .NET source debugging was because of "proprietary undocumented interface blah blah". Now that .NET is open source, can we convince the debugging team to finally release an external build of windbg with .NET source level debugging?
This would be incredibly helpful for so many different development and troubleshooting scenarios. For example, when developing services, there are those times where you really need to debug service startup using the kernel debugger. In other scenarios, it is much easier to xcopy cdb or ntsd onto a target and then connect to it remotely without having to deal with the chaos of MSI installing some package on a target in order to do a live debug from a remote machine using "heavy" IDE tools. There are many valid situations where MSI installing such tools is unacceptable and/or undesirable.
To this day, the Debugging Tools are unmatched in their power in the right hands. It is a shame that only internal Microsoft folks can source level debug .NET code with them.
Spoken another way. SOS is unmatched when compared to debugging .NET code in IDEs. There is just no comparison! Yet only internal Microsoft folks can harness the power of SOS coupled with source level debugging.
Please open this up for the masses now that ,NET is open source.