For RTM, the plan is to update Sidekicks to expose additional functionality new to 2010; if you have any additional wishes now is the time for the feedback – drop us an email at tfs_at_attrice_dot_info.

Prior to debugging you need to know about several limitations desktop build has comparing to Team build running on the server. From MSDN article ”How to: Build Team Projects on a Desktop”:

• The desktop builds perform only the compilation and tests.
• They do not perform other public build steps such as getting sources from version control, updating work items, labeling sources, creating new work items, and copying to drop locations
• The default MSBuild logger logs the results because the Team Foundation Build logger is not enabled for desktop builds.
• The desktop builds do not store build data in the database.
• They do not generate any status reports. Build output is written to console. You can learn more details by enabling the Verbosity option when running the MSBuild command. For more information, see MSBuild Command Line Reference.

1. Follow the directions in the article to get you all prerequisites for building Team Build projects locally in order.

2. Open local copy of Team Build project file from previous step with MSBuild Sidekick and define TeamBuildRefPath property in “Project Properties” pane. To do so access “Build” -> “Build Options” menu item, and then click “Project Properties” icon at the left pane and add TeamBuildRefPath property with its value set to “C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\” (or different drive where you have VS 2008 installed).

Reload project by clicking “File” -> “Reload”. A few warnings you still see do not affect further debugging.

3. Your Team Build project is now ready for debugging. You may start debugging by clicking Debug toolbar button or pressing F5 key.

You can learn more about debugging and how to use it efficiently from our previous posts “How to debug step-by-step with MSBuild Sidekick” and “How to review Properties & Items while debugging with MSBuild Sidekick”.

Download and try this new version right now! You don’t need to uninstall previous MSBuild Sidekick version, and no license is required for the beta (the beta expires on 01 May 2010). Runtime .Net 4.0 Beta 2 is required.

It’d be great if you email us about your user experience, found bugs and new feature requests. Final version MSBuild Sidekick v3 will be released after Visual Studio 2010 RTM.

The release functionality is mainly identical to that of version 2.4 for 2005/2008, with the exception of the following:
Permissions Sidekick: Sidekick is not available in this release (to be added back in 2010 RTM timeframe)
Build Type editing (VS integration only): The feature is not available in this release
Dynamic History support (VS integration only): the History toolwindow is updated only when it is visible alongside with Source Control Explorer and single instance of the window exists (in 2010 History toolwindow may have multiple instances)

For 2010 we still supply both stand-alone client application and Visual Studio integration package; the latter uses VS 2010 extension registration mechanism and is now available through VS Extensions Manager.

Please note that since object model API for 2010 release is still being finalized, we did not include any new features in the release for beta 2, relying instead on API backward compatibility (on which TFS team did an excellent job allowing us to provide same features as in 2008 with minimum changes). But we do plan on supporting TFS 2010 new features in our utilities; if you feel strongly about any features or want to provide other feedback, feel free to comment on the blog or reach us at tfs_at_attrice_dot_info.

The release 2.4 includes a relatively large number of bug fixes as well as couple of new features.

Features

• Labels Sidekick: Support filtering by file extension in Labels Comparison window
• Code Review Sidekick: Check-in policy violation indication shown next to changesets in a list
• Workspace Sidekick: Support ability to save list of found workspaces
• New Users View Sidekick: Show searchable list of user names and user display names in TFS Valid Users group

Bug fixes

• BUGFIX VS Integration (Dynamic History): exception thrown when viewing history on pending adds
• BUGFIX Code Review Sidekick: Changeset/Work Item selection dialogs do not keep last set of parameters set
• BUGFIX Code Review Sidekick: When all changesets selected, the list of changesets is not scrollable
• BUGFIX Labels Sidekick: Multiple selection of labels in list does not work with keyboard
• BUGFIX Labels Sidekick: Labels Comparison is out of sync for certain label content
• BUGFIX Status Sidekick: Undoing changes on root node ($\) causes an exception

Let’s conclude with short description of new Users View Sidekick. Sidekick works around known limitation in TFS version control, where it displays only user names for item history or other version control dialogs. In some corporate environments user names tend to follow cryptic conventions set by IT which are completely unrelated to actual user first and last name (such as GERWA12N etc.). In such scenarios, Users View Sidekick would allow you searching for actual user display name using AD user name.

Caveat that applies to the usage of Users View Sidekick – retrieving user names through TFS OM API may potentially take quite a long time.

In this post we shall touch upon important feature of MSBuild Sidekick debugger – namely inspecting Property and Item values during debugging with Globals and Autos windows.

The walkthrough below will show how to review Property and Item values while debugging:

1. Start debugging project in step-by-step mode (see previous post)

2. When Target/Task is selected (highlighted with bold border in Debug window) click on View > Globals Window and View > Autos Window menu.

Globals and Autos windows will appear at bottom pane of main application window.
Note: you may simply change these windows position by dragging-and-dropping them anywhere on application window.

Globals window displays Property and Item values as they are evaluated during the build execution. 

Autos window is similar to Globals window but displays only Properties/Items that are defined as input or output parameters for Target/Task element to be executed at the next step as you step through the project.

3. Now let’s review the data. One can use Show combo box to switch between Properties and Items view mode.
Data is organized as a table with the following columns:
  * Property/Item name
  * Property/Item current value

4. You may also use Filter text box to filter currently visible elements based on element name.

5. As you click on “Debug Step” button and debug step-by-step you may see that Properties/Items that have been changed on previous step are highlighted in red.

Now you can debug your projects without ever adding extra “Message” tasks while reviewing build execution in real time – jut use MSBuild Sidekick debugger and resolve problems in your builds in no time.

In this post we shall show how to debug typical C# console project with MSBuild Sidekick.

1. Create new C# Console Application project with Visual Studio and open the project with MSBuild Sidekick.

2. Click Debug Step button (or press F11 key) to start step-by-step debug. 

3. You can see now build execution order in Debug Window that should appear automatically. You may also open Debug Window by clicking on View -> Debug Window menu item.
Note: Debug window appears in floating mode when it is opened for the first time. To make Debug window docked drag-n-drop it at desired location on MSBuild Sidekick main application window.

 
4. Once in Debug mode, you can debug step-by-step by clicking Debug Step button (or pressing F11 key). MSBuild Sidekick highlights diagram elements differently depending on their current status:
* Current Target \Task is always highlighted with bold border
* Targets\Tasks that were successfully executed are highlighted in green
* Targets\Tasks that were skipped are highlighted in yellow
* Targets\Tasks that are not yet processed are not highlighted
Note: You may always see color coding rules by expanding legend which is collapsed at bottom of Debug Window.
 

5. To stop build execution on a specific Target\Task you may set breakpoint on it. To set breakpoint for Target\Task open right-click context menu and choose Toggle Breakpoint item.
 

6. Target\Task with breakpoint becomes marked with red circle.

 
7. Click Debug button (or press F5 key) to continue debugging.

8. Once build execution reaches Target\Task with breakpoint set, MSBuild Sidekick will switch into step-by-step debug mode. Current Target/Task will be highlighted with bold border around it in Debug window.

In MSBuild Sidekick v 2.3 we introduced integration with MSBuild Extension Pack tasks; now you can add, edit properties and view online help for all the MSBuild Extension Pack tasks in the Sidekick application.

To illustrate these features let’s create new MSBuild project in MSBuild Sidekick v2.3 and add a MSBuild Extension Pack task to it.

Note: you should have MSBuild Extension Pack properly installed; it is available at http://www.codeplex.com/MSBuildExtensionPack.

1. Right click on Target element and choose “Add Task” from context menu.

2. In the “Add Task” dialog choose “Custom Tasks” tab – you should see there all the MSBuild Extension Pack task classes.

3. Then click on task class you’re going to use in your project, click “Add” button and click “Close” to leave dialog window.
Note: you can add multiple tasks using “Add Task” dialog by clicking “Add” button multiple times.

4. Choose relevant task action in TaskAction property drop-down for your new task.

5. Once task action is selected, the task parameters list will be filtered automatically, so that only task parameters relevant for the selected task action will be displayed. Required input parameters will be marked with asterisk (see Format parameter on the screenshot above).

6. To view online help for the selected MSBuild Extension Pack task navigate to Help window.

Many of you would remember “How would you spend $100 on MSBuild?” poll published on MSBuild Team Blog. MSBuild users were asked to vote on most valuable future features in MSBuild; and while we could not improve MSBuild engine performance or add inline tasks support we did implement visual debugger for MSBuild! MSBuild Sidekick v2.3 is now the one-stop solution for all your debugging needs such as stepping through the build, inspecting locals and setting breakpoints.

The new features in MSBuild Sidekick v2.3 are:

• Visual debugger (you can analyze build sequence using diagram) with breakpoints support and integrated Globals/Autos windows for viewing properties/items values during debugging

• Customized editors and integrated online help for MSBuild Extension Pack tasks
• Ability to cancel a running build
• Ability to edit Project element raw XML
• Auto-detection of latest .NET Framework on tool installation

Please note, that for all registered users the upgrade to new version is free of charge; otherwise the license can be purchased online.

Please see product page for additional information; also make sure to have a look at walkthroughs detailing the application usage and the user manual.