Patrick’s Bytes

Teaching debugging and exception handling in Visual Studio today and some interesting questions pops up. Among them is how come certain variable’s value cannot be changed during debugging while the others can?

I haven’t found a solid answer yet except from frice’s blog:

Like the Immediate window, sometimes you can change local variable values by selecting the variable you want to change and clicking the Value box. If VB lets you to change the variable, the Value field will let you edit it. Some things can’t be changed though. For example, you can’t change objects, such as the properties of a control, or certain Variant variables. In cases where you can’t change the values of a variable in the Locals window, you can use the Immediate window to test the change.

Below are some related articles/ blog post.

VS 2005: Cool debugging tricks

Basic Debugging features in Visual Studio 2005

New debugging features in Visual Studio 2005

Using the latest materials from Ervin to teach Getting Started with .NET for Start.NET program today at MCSB training center at Island Plaza, Penang. The first shock early morning is almost all the Visual Studio 2008 installation complain about trial expiration. I taken about 2 hours to figure out actually some itchy hands changed the system date of the training PC back to year 2007, thus triggering the VPC to complain about expiration.

Finished 4 out of 8 labs today and materials from Ervin are generally good and easy to understand but I realize a few places where it will do good to have some extra explanation. So on the spot during the training, I came out with a PPTX of about 7 slides to give examples on Object Oriented programming concept.

You can download it from SkyDrive here.