Clik here to view.
#849 – Using the Call Stack in Visual Studio to Navigate within Your Code
When in break mode within Visual Studio, you can view the call stack in the Call Stack window. When you bring up the Call Stack window, there will be a yellow arrow pointing to the top of the call...
View ArticleClik here to view.
#875 – Looking at the Call Stack after Catching an Exception
After an exception is thrown, it bubbles up the call stack until a handler that can handle the exception is found. If you set a breakpoint in an exception handler, you can then use the debugger in...
View ArticleClik here to view.
#912 – Intellisense Can Show Exceptions that a Method Might Throw
In some cases, when the Intellisense function within Visual Studio shows you information about a method that you are going to call, it will also list potential exceptions that the method might throw....
View ArticleClik here to view.
#914 – Using the Debugger to Break when an Exception Is Thrown
By default, if you have an exception handler defined, the debugger in Visual Studio will not break (i.e. stop) at the point where an exception is thrown. You can, however, configure Visual Studio to...
View ArticleClik here to view.
#957 – Naming Files that Contain C# Code
Files that contain C# code are typically named using a .cs extension. You can, however, include C# in a code having any extension you like. Note that in Visual Studio, if the extension is other than...
View ArticleClik here to view.
#966 – Visual Studio Code Editor Helps with Indenting
You’ll typically use a consistent indent level in your source code to assist with readability. Visual Studio helps by automatically indenting your code as you enter it. For example, if you enter an if...
View ArticleClik here to view.
#1,090 – Using Visual Studio to Verify How Floating Point Numbers Are Stored
Recall that floating point numbers are stored in memory by storing the sign bit, exponent and mantissa. We showed that the decimal value of 7.25, stored as a 32-bit floating point value, is stored as...
View ArticleClik here to view.
#1,184 – Managing using Directives, part I
As you write code, Visual Studio will let you know that you’ve used an identifier that it doesn’t know by marking it with a red squiggly underline. Below, we’ve started creating a class that derives...
View ArticleClik here to view.
#1,185 – Managing using Directives, part II
You can add missing using directives by using the Resolve command. You can also clean up the current list of using directives in a file, removing the ones that are no longer needed. You can remove...
View ArticleClik here to view.
#1,213 – Visual Studio 2014 – Unused using Statements Greyed Out
In Visual Studio 2014, the editor will grey out any using statements that are not required. This is done at build time. Note that you can still use the Remove Unused Usings command to remove any...
View Article