Mario Hewardt has just published a new course: Introduction to .NET Debugging using Visual Studio 2010
This course teaches how to use the Visual Studio 2010 powerful debugging features to hunt down tough bugs. You might be surprised that Visual Studio contains super powerful debugging features that are invaluable when hunting down tough bugs. Topics such as data inspection, power tools, debugger canvas, threading and much more is explained. We even take a look at some of the new debugging features in Visual Studio 11 beta.
Pluralsight, thank your for your offering of wonderful courses over the years !
However……
The coverage of Symbol server in Module II of this course, as just one example, is fragmented and incomplete. The author ignores the obvious and adds more to confusion than to clarity.
In addition, he spends more time describing what he is doing rather than helping the viewer understand the motivation for doing it.
All in all, I would not recommend this course to those considering viewing it.
Thank you for your feedback RM.
Symbols and symbol servers (including how to setup your own) are covered at great depths in the Advanced Windows Debugging Part I course. Feel free to take a look at that and if if you have any questions please do let me know (marioh@thehightechavenue.com).
Thank you for the course.
Viewers like me would have benefited a lot more if the author had demonstrated remote debugging instead of showing SOS and other less-used features.
Remote debugging is a reality faced at all production installations and I was surprised that although the author alluded to it in the opening module, it was not mentioned or explained again during the remainder of the course.
Thank you for your feedback RM.
Live debugging in pure production environments is most commonly not allowed due to the downtime required when live debugging is being performed. Furthermore, Visual Studio remote debugging requires configuration changes on the target machine (openining up firewall) that the operations team normally will not allow. Most commonly, debugging in production environments is done through postmortem debugging. Until recently, the native debuggers were really the only choice but with postmortem support in Visual Studio 2010 coupled with SOS integration VS became a very viable approach.
Thank you for your quick response. Appreciate it !
Per your comments, I take it then that the Remote Debugging Monitor (msvsmon.exe) offering from Microsoft is just of academic interest.
Thank you again for taking the pains to put together this nice course for our benefit.
In reply to:
“Per your comments, I take it then that the Remote Debugging Monitor (msvsmon.exe) offering from Microsoft is just of academic interest.”
In contrast to production environments, if you have an environment where you control the machines and can make configuration changes, Visual Studio remote debugging may be of interest to you.
Thanks,
Mario