Creating an application consists of writing code for accessing and updating data structures. This seems simple but does require a good knowledge of the data structures available in .NET, together with the instructions provided in C# for organizing the execution of the code.
When something doesn’t happen as planned, we call it a bug, referring back to insects that caused electronic component malfunctions in the early valve computers. Once the code has gone off to production, it is necessary to find a means of monitoring application health and detecting runtime errors: this usually involves writing messages in files or making them accessible remotely.
However, once the deviant behavior has been identified:
How can you get back to the source of the problem?
How can you find out which section of the code is not performing the expected process?
How can you access the status of the application data?
In this course, you'll learn how to hunt down bugs with Visual Studio. We’ll examine concrete cases using unit tests to present tools, methods, hints, and tips.
Join us on this course, and you'll be able to debug any .NET code!
