How to create a bootable USB flash drive to install Windows 8 Developer Preview

Like many folks, after watching the BUILD keynote this morning, I couldn’t wait to get home and install Windows 8 Developer Preview on my laptop. The instructions for installing Windows 8 are simple enough. The only fly in the ointment is that installing Windows 8 requires a DVD to create an install package. Of course,…

14

Visual Studio 2010 RIP List (Partial)

Like any software product, with every new release of Visual Studio, we add numerous new features to support additional scenarios, improve existing features based on customer feedback and occasionally, we remove some features based on a number of factors such as lack of customer demand, quality issues, retirement of legacy technologies, changing industry trends, etc….

6

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

One bug, two developers: Collaborative debugging is now a reality in Visual Studio 2010

Quite often, one or more developers need to collaborate on a bug to figure out the root cause of the problem. This collaboration is typically done using tools like email, bug tracking system (e.g. TFS) or if the developers are collocated, they might work on the bug together in one of their offices. Here is…

6

Looking for questions or feedback on IntelliTrace

During the last few months, I’ve been blogging extensively about a new Visual Studio 2010 feature called IntelliTrace (formerly known as the “Historical Debugger”). We are very excited about IntelliTrace and think that it’s going to change how people debug their applications. Since IntelliTrace is a brand new feature, we are eager to hear from…

4

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

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

Managing Breakpoints in Visual Studio 2010 using Breakpoint Labels

One of the new features that we’ve added to the Visual Studio 2010 debugger is the ability to manage breakpoints more effectively. You might say that the existing Breakpoints window is a fine tool for being able to manage your breakpoints. After all, you can create, modify and delete breakpoints using the Breakpoints window which…

2

Importing and exporting breakpoints in Visual Studio 2010

In Visual Studio 2010, we have added the ability to import and export breakpoints. There are several scenarios where being able to import/export breakpoints is useful. For example, you can share breakpoints with other developers in your organization. Example: Hand off bug to another developer Here is a quick walkthrough that shows how to use…

2

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

In part III of the coverage of the Historical Debugger, I’m going to look at another scenario of the Historical Debugger which is the ability to record and playback manual test failures. One of the problems areas in software development that really impacts productivity is non-reproducible bugs which are code defects that only occur in…

2