Understanding Common Language Runtime Debugging Services

Common Language Runtime debugging services are provided by the tool DbgCLR.exe. Invoking this tool gives you a graphical interface that helps the developers to debug the program that are written in the .Net framework and that target the CLR.

However there are some exceptions in using the CLR debugger. It is not possible to implement the CLR debugger remotely and it does not support Win32 applications that are written in native code. It does not support F1 help and Autos window. Implementation of the Disassembly window and Registers window are done in the CLR debugger.

You can fine the DbgCLR.exe program in the GuiDebug folder of the .Net framework installation. Just start this program and from the debug menu you can select the program that should be debugged. Make sure to select the program and to set the working directory to the directory in which the program is available. Now open the program to be debugged.

There is an Arguments box that allows you to key in the arguments if any that is needed by the program that is debugged. Now you can open the source files that you want from the File menu and click OK. This creates the solution for the session. You can use the Save File As to save the solution is needed.


Recommended Resource

| Understanding Common Language Runtime | Understanding the benefits of .NET - Common Language Runtime | Understanding Common Language Runtime Debugging Services | How Common Language Runtime helps expediting your development process | What is Common Language Runtime | Using the Microsoft Common Language Runtime Profiler | Common Language Runtime Download |


“Amazon and the Amazon logo are trademarks of Amazon.com, Inc. or its affiliates.”

| Privacy Policy for www.dotnet-guide.com | Disclosure | Contact |

Copyright - © 2004 - 2024 - All Rights Reserved.