WitCustomControls for Visual Studio 2013 released!

Last week we published the 1.2.0.0 release of the WitCustomControls. This time Stéphane Lagacé has done most of the work of by updating the MultiValueControl with autocompletion and data binding. I’ll cover these features in a later post.

Other than the work from Stéphane, the controls have been recompiled against the 2013 assemblies.

The control pack contains the following work item custom controls:

  • MultiValueControl: a ComboBox to accept and show multiple values for a field by showing a list of checkboxes. More details here: MultiValue Control
  • ScreenshotControl: a simple control (button) to capture a screenshot as a work item attachment. More details here: Screenshot controls.
  • AttachmentsControl: this control cab be used as an alternative to the standard file attachments dialog. More details here: Screenshot controls.
  • WebBrowserControl: displays a web browser inside a work item. More details here: Web browser control.
To install the files, download the file matching your TFS version. For TFS 2012 and 2013 the .zip file contains an installer for the Windows controls and a .zip file for the Web Access controls.

Download the controls here.

Building a Release Pipeline with Team Foundation Server 2012

Last week Microsoft Patterns & Practices released a new guide about release management using TFS 2012. I had the opportunity to read the guide during development and it has both great guidance, hands-on labs and concrete tooling to support the process. I personally really liked the section on getting good feedback, where the authors shares some good examples on how to use TFS to understand and optimize cycle times in the release process. I definitely recommend taking a look at this guide if you in any way are involved in the software release process.

From the guide:

“The goal of this guidance is to put you on the road toward continuous delivery. By continuous delivery, we mean that through techniques such as versioning, continuous integration, automation, and environment management, you will be able to decrease the time between when you first have an idea and when that idea is realized as software that’s in production. Any software that has successfully gone through your release process will be software that is production ready, and you can give it to customers whenever your business demands dictate. We also hope to show that there are practical business reasons that justify every improvement you want to make. A better release process makes economic sense by providing:

  • Faster time to market
  • Better quality software
  • More productive employees

Follow the team at Trey Research as they refine their processes and move from a mostly manual pipeline to one that’s mostly automated.”

Start reading the guide here.