How to display the environment variables for a process in the Visual Studio debugger

Every process in Windows has what’s known as an "environment block" that contains the process’ environment variables and their values. Programmatically, you can display the environment variables for a process using the ::GetEnvironmentStrings() function. But there is a much easier way to view the environment block for a process in the Visual Studio debugger. When…

1

Size Specifier: How to display a C/C++ pointer as an array in the Visual Studio debugger

Viewing a C/C++ array in the Visual Studio debugger is easy. You can expand the array in the Watch window (or any other variables window) and see its values. For example, let’s say you have the following C++ code: int _tmain(int argc, _TCHAR* argv[]) { int numbers[3] = { 1, 2, 3 }; return 0;…


The Charles Babbage Difference Engine

This week, I was in Silicon Valley to talk to a number of ISV customers about what’s coming up in Visual Studio Team System 2010 for C++ developers. I’ve always wanted to go to the Computer History Museum and this time, I had a couple of hours before my flight back to Redmond so I…


An in depth look at the Historical Debugger in Visual Studio 2010 (Part II)

In Part I of this post, I talked about the Application Event Recording capabilities of the Historical Debugger. In this segment, I’m going to look at another capability of the Historical Debugger which is Playback Debugging or what some people refer to as Time Travel Debugging. Stepping Back in Time For many developers, the one…

1

An in depth look at the Historical Debugger in Visual Studio 2010 (Part I)

In one of my earlier blogs, I introduced a new feature in Visual Studio 2010 called the Historical Debugger that truly transforms how you debug applications. In this blog and subsequent blogs, I’m going to cover in depth how and when to use the Historical Debugger. The Historical Debugger supports six mainline scenarios: Application Event…

2

Using the WPF Visualizer to debug applications in Visual Studio 2010

WPF applications make writing rich client applications much easier but the main drawback is that debugging XAML is difficult. The Visual Studio debugger is very good at debugging imperative languages but when it comes to debugging declarative technologies like XAML, it’s mostly back to  "printf" debugging. For example, trying to debug data binding issues or…

3

New VSTS "Pep Talk" Videos

Today, our marketing team released a set of very funny VSTS “pep talk” videos. Here is one of them.   http://www.microsoft.com/visualstudio/en-us/products/teamsystem/default.mspx?pt_id=690_2   Thanks, HabibH.

2

Where to Download "The Goods" for PDC 2008

At last week’s PDC conference, the attendees were given a 160 GB USB External HDD that contains a slew of content which includes a number of SDKs, whitepapers, etc. This content is collectively known as "The Goods". The great news is that most of this content is available for download. Below, I have listed what…

2

What’s new in Visual Studio Team System 2010: Episode 2

Feature: Historical Debugger In my previous post, I mentioned that one of the key scenarios that my team is working on is eliminating the “No Repro” scenario. Let’s take a look at what this actually means. Let’s say that you’re a developer and you are trying to reproduce a bug in your code. This is…

6

What’s new in Visual Studio Team System 2010: Episode 1

Today, there were several announcements detailing the next version of Visual Studio and Visual Studio Team System. As a member of the Visual Studio Team System team, I thought it would be fitting to share a few more details about some of the scenarios that my team is enabling in the next version of Team…

3