Buck Hodges

Visual Studio Online, Team Foundation Server, MSDN

April, 2007

  • Buck Hodges

    Update to "How to run tests in a build without test metadata files and test lists (.vsmdi files)": Test Categories



    Pierre Greborio, a developer over in MSTV, has contributed a great new feature to the power tool task that allows you to run tests without .vsmdi files: test categories.  Those of you who have used NUnit are probably familiar with the Category attribute.  Test categories allow you to execute specific groups of unit tests.  To tag a unit test method as belonging to a category, just add the Category attribute.  Unlike the test container feature, the test category feature will not be in Orcas (if you'd like to see it in a future release, be sure to let these folks know).

    The new version of the TestToolsTask, targets file, and documentation are in an updated zip file attached to the original post, which has also been updated (download here).

    While the details are discussed in the TestToolsTask.doc file, here's how to use it.

    Using the new Category attribute

    IMPORTANT NOTE: The Category attribute feature will not be included in Visual Studio Codename Orcas.

    The Category attribute must be specified for every test method that should be included in that test category. Note that there is no way to specify that all tests not in a test category should be run.

    In order to use categories you need to:

    1. Add a reference to Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll in your project.

    2. Add the namespace in the code:
    using Microsoft.TeamFoundation.PowerTools.Tasks;

    3. Add the Category attribute to the test method:
        public void MyTestMethod()
            // TODO: Add test code here

    Finally, you will either need to specify the TestCategories in TfsBuild.proj if you are using Team Build or modify your project to call the task directly.

    Pierre both wrote and tested the code (making heavy use of Reflector in the process).  Thanks, Pierre!

    The other feature that's new in this release is the support for test names.  This just exposes the equivalent to the mstest.exe /test command line switch.  The name that's specified is implicitly a wildcard match.  Specifying "Blue" as the test name, for example, will execute every test method that has Blue in the name, including DarkBlue and BlueLight.  The TestName property will be available on the Orcas TestToolsTask (beta 2 and beyond).  The details are described in the documentation file.

  • Buck Hodges

    Guidance for Structuring Team Projects in TFS 2005


    Brian Keller points out that Doug Neumann's Guidance for Structuring Team Projects is now available on the Microsoft Team Foundation Server Branching Guidance CodePlex project.

    Guidance for Structuring Team Projects

    - Doug Neumann - Microsoft Corporation


    One of the most important considerations when looking to deploy Team Foundation Server within your organization is how you will employ the “Team Project” concept. It can be very tempting to jump in and immediately start creating Team Projects to satisfy every whim of the users in your organization. However, restructuring existing team projects is difficult to accomplish, so establishing a strategy for using team projects up front is very important. Careful forethought now can save you much pain down the road.

    This whitepaper provides details on the components of a team project and discusses how those components may impact your decision about structuring your team projects. It also lays out a set of common strategies for employing team projects. Understanding this base of knowledge should empower you to make the best decision on how your organization will use team projects with Team Foundation Server (TFS).


    Keep in mind that while the overall concepts will apply to both TFS 2005 and Orcas, some of the details on how to accomplish things will change in some areas, and Team Build in particular.  For example, the part that talks about Team Build Types points to a blog post on how to force Team Build into building code that spans team projects.  In Orcas, that workaround is not needed.  You just create whatever workspace mappings you need for your build in the new build definition dialog.

    tags: , , , ,

  • Buck Hodges

    Using an ASP.NET TFS data source


    Kannan Sundararajan has written a couple of posts on how to use TFS as an ASP.NET data source.  If you are interested in displaying TFS data in ASP.NET-driven web pages, you'll want to check it out.

    First he shows you how to build the data source and gives you the code that you need to build the dll.

    TFS Data Source ASP.NET Control

    While learning ASP.NET for developing the RTE for MSDN Forums I had to interact with multiple teams and provide them with status reports on the work items. Some of them were not using TFS yet for that code base. So I wanted a way to easily write a TFS report, send the url to all these teams.

    Given my earlier TFS background and the capabilities I learnt exist in ASP world thought why not leverage these two and thus began this exercise to write a TFS Data Source ASP.NET control which I can drop into any ASP.NET web page, bind it to any existing ASP.NET controls to create a simple TFS report.


    Then he shows you what you can do with it and walks you through the steps of building a web page that uses the data source from the previous post.

    TFS Reporting Simplified

    In my last post we saw how to write a TFS Data Source Component. In this one I will explain how to use them to generate a TFS report like the one below leveraging existing ASP.NET controls.



    tags: , , ,

  • Buck Hodges

    Orcas Beta 1 has shipped - summary of Team Build beta 1 features and links


    As you probably already know, Orcas Beta 1 has shipped.  Internally, the product team is focused on finding and fixing bugs for beta 2 (and has been for nearly a month now).

    The release includes a Virtual PC image with all of Visual Studio Team System plus Team Foundation Server, which you can download now.  There's also an image that has only VSTS on it, but that's not nearly so interesting, right?  ;-)

    Be sure to read all of the instructions on the download page.  The release is in the form of a base image, which was also used for the March CTP, and a differencing disk image with the Orcas release on it.  If you've already gotten the base image from the CTP, you don't have to download it again.

    From Brian's updated roadmap, here's the high-level list of features in Orcas Team Build beta 1.  Items marked as "new" were not in the March Orcas CTP.  I've added links to blog posts for each of the features.

    Build (interview/demo, screencasts)

    • Support multi-threaded builds with the new MSBuild.
    • Continuous Integration – There are many components to this, including build queuing and queue management, drop management (so that users can set policies for when builds should be automatically deleted), and build triggers that allows configuration of exactly how when CI builds should be triggered, for example – every checkin, rolling build (completion of one build starts the next), etc.
    • Improved ability to specify what source, versions of source, and other build properties (BuildStep task, GetBuildProperties and SetBuildProperties tasks).
    • Improved extensibility of the build targets – such as ability to easily execute targets before and after each solution/project is built.
    • Improved ability to manage multiple build machines (see extensibility, screencast).
    • Stop and delete builds from within VS.
    • .NET Object model for programming against the build server (another example; using it via PowerShell: here, here, and here).
    • Simplified ability to specify what tests get run as part of a build (TestContainer support is in Orcas).
    • The ability to store build definitions anywhere in the version control hierarchy (see extensibility).
    • Scheduled builds (new) - You can schedule builds to happen at specified times.
    • Improved build agent communication (new) - We replaced .NET binary remoting with WCF web services, simplifying some configuration and security aspects.
    • Ability to run GUI tests as part of a build (new) - Automated builds used to run tests in such a way as to prevent access to a GUI desktop.
    • New checkin policy for broken CI builds (new) - Preventing checkin while the CI build is broken.

    We've made a very large number of improvements to the build process in the form of overridable targets, properties, and new tasks.  We made a substantial effort to address many of the issues that have come up in the MSDN build automation forum where things were either not possible in v1 or required hacks.  We hope that our efforts in Orcas will show that we are listening and responding.

    In beta 2, there is support for client certificates (X.509) and HTTPS communication from the application tier to the build agent.  The result of our work there is that it's much easier to have a build agent exposed to the internet.  Our extranet support in build is still not as good as it should be, so there will likely be more work in this area in Rosario.  The changes in Orcas beta 2 are a big improvement, though.

    There are a few areas without links, and I plan to update this post with those links as I write about them.

  • Buck Hodges

    Visual Studio Team System chat - April 27, 2007 (this Friday)


    Join members of the Visual Studio Team System product group to discuss features available in Visual Studio Team Foundation Server, Team Editions for Architects, Developers, Database Pros, and Testers. In addition, discuss what's new in the in the Visual Studio code name “Orcas” Beta 1 releases for Team Suite and Team Foundation Server.

    Join the chat on Friday, April 27th, 2007 from 10:00am - 11:00am Pacific Time.

    Add to Calendar

    Additional Time Zones

    [UPDATE 4/26/2007]  There's now a second chat on Friday.

    Join the chat on Friday, April 27th, 2007 from 4:00pm - 5:00pm Pacific Time.

    Add to Calendar

    Additional Time Zones


    Technorati tags: , ,
  • Buck Hodges

    TFS Migration and Synchronization Toolkit pre-release published on CodePlex


    Matt Mitrik, the program manager for the TFS migration tools, has announced the availability of the first pre-release version of the Team Foundation Server migration and synchronization toolkit.  If you are looking into how to migrate away from a different bug tracking or version control system, this is where you'll want to start.  Be sure to let Matt and company know what you need in order to be successful!

    Migration and Synchronization Toolkit Prerelease Published on CodePlex

    A prerelease of the Migration and Synchronization Toolkit has been released on CodePlex! If you are interested in seeing the progress that we have made to date, and are eager to try out the sample tools, please visit the project site on CodePlex at http://www.codeplex.com/MigrationSyncToolkit


    Brian Harry has also written a bit more about the future plans for the toolkit.

    Migration and Synchronization Toolkit Prerelease

    We plan to build or to work with 3rd parties to build integration between TFS and a variety of other systems.  In the toolkit, you'll find initial samples for synchronizing TFS with Sharepoint (both documents and work items/lists).  Ideas we are pursuing include:

    • Sharepoint synchronization - Allows you to leverage TFS's branching, merging, unified backup, etc while exposing all of your data through Sharepoint in a clean way.
    • TFS <-> TFS migration/synchronization - Enables a variety of scenarios, including a poor man's project move, multi-master replication for distributed teams who want local copies of all of the data and more...
    • Project Server synchronization - Making it easier to keep TFS and project plans in sync.
    • ClearCase migration/synchronization - Enabling the two systems to coexist nicely when needed.
    • And more...


  • Buck Hodges

    How quaint: 1,000,000 files and 10,000 changesets


    I wrote posts when we hit 1,000,000 files (Nov. 18, 2005) and 10,000 changesets (Sept. 26, 2005) on the DevDiv server.  When you look at the April 2007 statistics (April 18, 2007) for that server, we're at 77,658,652 files and 204,556 changesets.  Clearly, that's a huge change in roughly 18 months.

    The file count climbs dramatically every time we add a new branch.  A full branch has about 3 million files.  Normally, we add a partial branch (1 - 2 million files).  So nearly all of the growth in files comes from creating new branches.

    The increase in the number of changesets is largely due to a tool listed in the table at the end of Brian's post.  There's tool called SyncDepotToMaddog checks in changes to TFS whenever changes are made in Maddog, which an application used by the QA folks.  It checks in a lot.  The changesets weren't going up nearly so fast until that thing was unleashed (quite a while back).

    If you are wondering where the application name comes from, we set the user agent string in the HTTP header for each web request to be "Team Foundation (<exe name>, <exe version>)" so that it is recorded in the TfsActivity database (tbl_Command).  You can read about how to use it in this post and that post.  We have the turned on for the DevDiv server, and that's what Brian uses to keep track of the requests and look for performance issues.

    tags: ,

  • Buck Hodges

    VSTS Testing: Using Fiddler to record VSTS web tests


    Sean Lumley, a developer on the VSTS web test team, has written a series of posts on using a new version of Fiddler to record web tests.  Sean worked with Eric Lawrence, who developed Fiddler, to incorporate new features that make this process much easier than in the past.  If you do any web testing, you'll want to check this out.

    Here's a high-level description from Ed Glas, who leads the VSTS web test team.  By the way, check out Ed's list of web and load test improvements for Orcas to see what's coming in the next release.

    We have released to web a new version of fiddler with a great new set of features around saving web tests. It is available at http://www.fiddler2.com/fiddler2/.

    Credit to Sean Lumley for delivering these features, and thanks Eric for this cool tool that we could add onto.

    Fiddler already had the ability to record AJAX and javascript popups, but it didn’t fixup the tests like the web test recorder does.

    Now, fiddler will apply a bunch of fixups to the generated web test:

    1) ASP.NET viewstate and event validation correlation

    2) Dependent request filtering

    3) Redirect filtering

    Furthermore, Eric has added HTTPS support, so fiddler2 can record over HTTPS!

    Even more exciting (to me at least, being the geek I am), is the new extensibility hook we provide in the web test save code. The features above (modulo the redirect filtering) were done using a new API we’ve provided. Like web test plugins, fiddler web test save plugins enable you to hook the save code to modify the resulting web test by changing or deleting requests.

    The most powerful thing this enables is for you to write a plugin that will automatically correlate dynamic variables for a given application type. For example, an SSRS plugin would fix up the web test to automatically extract and bind the sessionid querystring parameter.

    First, Sean goes into the details of the new features in Fiddler.

    Enhanced web test support in Fiddler

    If you have ever had trouble recording a web site with the web recorder included in VSTS, then we have probably suggested recording the same site with fiddler and looking for requests that the VSTS recorder did not capture. If you are not familiar with Fiddler, here is a short description from the fiddler site, “Fiddler is a HTTP Debugging Proxy which logs all HTTP traffic between your computer and the Internet. Fiddler allows you to inspect all HTTP Traffic, set breakpoints, and "fiddle" with incoming or outgoing data.” The author of fiddler included the ability to save a fiddler recording session to a VSTS .webtest file. Although the file saved was a valid web test, there were a few problems.

    1. The saved test included all dependent requests such as images, css file, js files, etc.

    2. It included requests that were the results of a redirect.

    3. The test did not correlate any hidden fields for you. i.e. viewstate

    So although you could save a test, it was not saved the same way the VSTS recorder would save it.

    I have been working with the owner of Fiddler to add enhanced web test support and he just recently released the updated version of fiddler to the web. You can get the updated version at http://www.fiddler2.com/fiddler2/. Here is a list of the new features:

    · Ability to filter out dependent requests

    · Only first request in a redirect chain will be saved.

    · Automatic correlation of view state and event validation fields

    · Plug-in architecture that allows you to write your own custom code that can change how a web test is saved.

    I will discuss the last point in detail in a later post. I will walk through the other changes below.


    Then he shows you how to write a web test plugin for Fiddler.

    Writing Fiddler Web Test Plugins

    My last blog post discussed changes made to fiddler which added enhanced support for saving web tests. This post will go into more detail about the changes and show you how to write your own custom code which can modify the way a web test is saved.

    The main change we made for saving web tests was adding a plug-in architecture which is very similar to Web Test Plug-ins and Web Test Request plug-ins. The new architecture provides you with a hook into the web test save code so that you can modify what is written to the web test. Each of the new filter type features listed in my previous post were written by writing FiddlerWebTest plug-ins. For example, the FilterByExtension plugin loops through each request that would be written to the web test and flags certain requests to not be written based on certain extensions.

    Let’s walk through the process of writing a new plugin. We will write a plugin which will automatically correlate dynamic fields associated with a SQL Server Reporting services site. This is the same reporting site I blogged about in this post: Debugging a Web Test. There are 2 dynamic fields which always need to be correlated for the reporting site that I am testing. They are the ExecutionID and the ControlID. By correlated, I mean that we need to the following:

    1. Add an extraction rule to the first request to pull out the values for these fields for the current session

    2. Then each time a subsequent request uses these parameters, bind them to the values extracted in the first step.


    Finally, he's posted a simpler web test plugin to help you get going.

    Another Fiddler Plugin Example

    Here is another example of a fiddler plugin.  This plugin will loop through each request and mark a request to not be written to the web test if it ends in a particular extension.  This example shows you how to flag requests to not be written to the web test by setting the WriteToWebTest property on the Session object.  Please see my previous post for how to deploy the plugin: Writing Fiddler Web Test Plugins



    tags: , , , , ,

  • Buck Hodges

    Configuring Visual Studio 2005 Team Foundation Server with Windows SharePoint Services 3.0


    [UPDATE 7/26/07]  Final guidance is now available.

    Brian Keller has posted information on how to get WSS 3.0 to work with TFS 2005, which has been a very popular request.   This approach has been designed such that the server will still be serviceable after the change (i.e., you'll still be able to apply patches and upgrade to Orcas).

    Configuring Visual Studio 2005 Team Foundation Server with Windows SharePoint Services 3.0

    Now that Windows SharePoint Services 3.0 is available we have received several inquiries from people wanting to use WSS 3.0 with Visual Studio 2005 Team Foundation Server. While we have stated that the next version of Team Foundation Server (code-named "Orcas") will support WSS 3.0 out-of-the-box, some customers have understandably wanted a solution sooner than this. There are even a few posts in the community (most notably from Mike Glaser who did a lot of groundbreaking work here) who have demonstrated how to get WSS 3.0 working with Team Foundation Server. However, the problem we observed with the community guidance is that it can leave Team Foundation Server in a state which is not serviceable (see the Q&A below for more information on what this means). Therefore we have prepared the attached guidance to help users enable WSS 3.0 to work with Team Foundation Server in a manner which will remain serviceable.

    Please note that this guidance is a "release candidate" of guidance which will eventually be posted to MSDN. We wanted to get this guidance out as soon as possible and address any user feedback on this version prior to posting the final version on MSDN. Please email Brian Keller if you have any feedback on the documentation. Also, as we are trying to get a sense for how many people have used this guidance, please also let us know if you are successful deploying this guidance and which option you went with (Remote or AT).


    tags: , , ,

  • Buck Hodges

    TFS tools on CodePlex (April '07)


    Sébastien Monteil, C# MVP, sent me email about a tool on CodePlex called Fissum, which is a tray app that shows your work items.  That reminded me that back in September I wrote a post listing the tools for Team Foundation Server on CodePlex.  So I thought this would be a good time to post a new list.  It's great to see that the list has gotten quite a bit longer!  It's in popularity order, according to the search that I did on CodePlex.

    Expand Microsoft Team Foundation Server Branching Guidance

     - Microsoft Team Foundation Server Branching Guidance

    Expand Team Foundation Server Administration Tool

     - Member of the Power Toys for Visual Studio Collection - TFS Admin Tool allows a Team Foundation Server administrator to quickly add and modify user permissions to all three platforms utilized by TFS through one common interface.

    Expand Automaton

     - Automaton is a Continuous Integration engine optimized for Team System and Team Builds. Included is the TeamFoundationExtensions class library which includes helpers and tasks for TFS and MSBuild.

    Expand TFS Source Code Version Tree Browser

     - This project aspires to create a Version Tree Browser for Team Foundation Server allowing for the visual presentation of branches, merges and version information. The exact format and requirements will be determined as part of this project based on published best practices, similarly mature related product features and TFS version control specific feature sets.

    Expand TFS Plug-in for CruiseControl.NET

     - A plug-in to allow communication with Team Foundation Server for the popular open source build automation tool CruiseControl.NET

    Expand Team Foundation Server Event Subscription Tool

     - A GUI tool for subscribing to events on a Team Foundation Server, equivalent to the command line bissubscribe.exe tool. It is deployable to client workstations, whereas bissubscribe.exe only exists on the Team Foundation Server. Project is originally based on the code at Naren's website ( http://blogs.msdn.com/narend/archive/2006/07/26/679440.aspx )

    Expand TfsAlert

     - TfsAlert is a Windows System Tray application which monitors for subscribed TFS notifications and will display a balloon window accordingly. In addition to notifications a user will have the ability to control limited TeamBuild functionality.

    Expand TFS Work Item Explorer

     - The Visual Studio Team Explorer work item datasheet view is quite limited in functionality. The TFS Work Item Explorer tool allows developers to define their own custom drilldown tree of WIQL queries in an XML file (“template”), leveraging global values (e.g. server name, project name, etc.), field values (of parent queries of any generation) and custom field configuration (e.g. display the 'Assigned To' field as 'Developer' and make read-only). Each TFS project can be associated with its own template via the application configuration file.
    Out of the “box”, TFS Work Item Explorer includes a Scrum for Team System template, which mimics the behavior of the now deprecated Scrum Explorer tool. Currently, read-only access to work item is supported but full write support is planned in an upcoming release.

    Expand TFS Code Review Workflow

     - TFS Code Review Workflow
    This project is a combination of a Code Review Work Item and a Code Review Check-in Policy. The check-in policy doesn’t allow a check-in unless it has an associated Code Review work item, and that work item is set to approved. Only people in a TFS group named [Project]\Code Reviewers can set an item to approved.
    1. Dev finishes code and wants it reviewed so they shelve the changeset and create a Code Review work item and mention the name of the shelf set. This is assigned to a general Code Review team.
    2. People on the code review team have event subscriptions which sends them an e-mail when a workitem is assigned to the Code Review group. One of them will open the work item, review the shelf set and resolve the item as 'Accepted' or 'Needs changes' which assigns it back to the original dev.
    3. Once in an approved state the dev can check-in and associate to the work item which will close it.

    Expand Custom Controls for TFS Work Item Tracking

     - SP1 for Visual Studio Team System comes with interesting custom control feature. Now we can develop and deploy our own custom controls to provide rich functionality in work item form. See here for how to develop a custom control: http://blogs.msdn.com/narend/archive/2006/10/02/How-to-use-Custom-Controls-in-Work-Item-Form.aspx .

    Expand Turtle

     - Turtle is a free, open source client for Microsoft Team Foundation Server source control services. It is an alternative to the VSTS plugin for Visual Studio, or for those who may be using using TFS for projects not compatible with Visual Studio.

    Expand Team Foundation Time Tracker

     - Team Foundation Time Tracker is small utility for tracking work time on any type of work item in Team Foundation Server

    Expand TFS Code Comment Checking Policy (CCCP)

     - This Team Foundation Server (TFS) checkin policy ensures that the source code contains code comments (/// for C#, ''' for VB.NET) for classes, methods, properties, fields and events before checking it into Team Foundation version control (TFVC).

    Expand TFS PowerPack

     - The TFS PowerPack is a set of tools for clients using the TFS server.
    The tools were made to satisfy needs and add more features not provided by the original installation of TFS.

    Expand TFSBuildManager

     - TFSBuildManager is a utility to manage Team Foundation build types in an environment other than Visual Studio.

    Expand VSSConverter GUI

     - GUI front end to the VssConverter command line utility that ships with Team foundation server

    Expand RDdotNET

     - RDdotNet is an entity for Research and Development of .NET frameworks, sites and applications that do something interesting. Sometimes these componenets will be fully fleged real-world solutions and others that will be pure R&D of the capabilities of the .NET Framework.
    RDdotNet Community Foundation
    This component is a framework for building a service orientated community site. It will consist of a number of services including teh WhiteLabel service allong with some other nifty services
    RDdotNet TFS WorkItem Tracker
    This component will allow develoeprs to trach how much time they have spent on a particular project's work items.

    Expand Fissum - A TFS tray icon client

     - Fissum in a TFS tray icon client. Fissum provides a fast access to your work items directly from a tray icon menu.

    Expand Scrum Explorer

     - Scrum for Team System is a free Agile Software Development Methodology add-in for Microsoft Visual Studio Team System, developed by Conchango, in collaboration with Ken Schwaber and the Microsoft Technology Centre UK. When using the Scrum for Team System Visual Studio.NET add-in, I disliked the flat datasheet-style work item view so much that I decided to write my own custom view called Scum Explorer. Scrum Explorer provides a sprint-centric drilldown treeview of the TFS scrum work items.

    Expand TFS Quick Search

     - A visual studio 2005 add in that allows the user to search multiple fields of TFS work items for a project. A common usage of this would be to allow the user to quickly search title, description and history of comments of all work items in a project (but more fields should be easy to add).

    Expand TFS Follow Branch History Add-in for VS

     - This Project come to fill the missing feature of viewing full History of an item following its branches.

    Expand TFS File Sync

     - Web Service for receiving notification of TFS check-ins and copying specified files to locations like UNC paths or SharePoint servers.

    Expand Team Explorer Extensions

     - The purpose of this project is to extend the experience and capabilities currently available on Team Explorer and TFS.

    Expand BHAL Project

     - This project aims at being a customizable orchestrator for managing Teams with the aid of Team Foundation Server. Please help add some value to the project by commenting on the vision statemen...

    Expand Team Foundation Server Manager

    Expand TFS AddIn - CheckOut and Get Last Version

     - This is an AddIn for Visual Studio 2005 to users that use Team Foundation Server.

    Expand Team Foundation Command Line GUI Suite

     - This project will attempt to facilitate all of the command line management services available with Team Foundation Server by presenting users with the option to pass necessary arguments to the command line via an integrated Graphical User Interface. The project kickoff includes a modest TFS Project Deletion utility. There is a lot of ground to cover in this arena, so all contributions are both welcome and appreciated.

    Expand TeamPatter

     - TeamPatter is a TFS integrated messaging tool that allows for communication with any user accessable via Windows Live Messenger or classic MSN messenger. The integration with TFS comes in the form that from within workitem screens or via commands used directly in the messenger window, IM conversations on work items and potentially additional artifacts can be stored with the work items and visible from the work item editors or any other display mechanism that might be desired.

    Expand VSTS Time Entry

     - An application you can use to keep track of time spent on a Team Foundation Server Project. The app writes updates the Task Work items Remaining Work and Completed Work fields.

    Expand TeFoSe.Net

     - This project will be a Team Foundation Server Client GUI with extended functionality.
    The GUI will look like the familiar Source Safe GUI offering developer specific features for queries against TFS.

    Expand TFSBuildLab

     - The TFSBuildLab is a project to simplify the day to day operations when using automated builds and Team System. The project will address issues such as

    - Continous integration
    - Scheduled builds
    - Automated build cleanup
    and more...

    Expand TFS Proxy add-in for visual studio .net 2005

     - This little plugin will allow you to switch tfs proxy servers or disable the tfs proxy. It's also possible by installing a webservice to enable the add-in to be automatically configured.

    Expand TFS Management Console

     - TFS administration tool, based on Microsoft Management Console (MMC) 3.0

    Expand Migrating from Subversion

     - The Subversion converter tool transfers files, folders, version history, branches, and user information from a SVN database to Team Foundation source control.

    Expand Team Foundation Server - Project Moving tool

     - A tool for moving Team Project items between servers.

    Expand Jira2Tfs

     - A utility application to import JIRA issues to a Team Foundation Server project.

    Expand Delete TeamBuilds

     - Deletes TeamBuilds from the TFS buildstore and buildserver from a build script (or a service)

    Expand Team Foundation Work Item Paste Attachment from Clipboard

     - This project implements a Visual Studio add-in so you can "paste" items directly as Team Foundation work item attachments from your clipboard. The most common use case are screen shots, bu...

    tags: , ,

  • Buck Hodges

    VSTS International Survey


    Aldo Donetti, lead PM on the VSTS globalization team, sent out email today about the newly released VSTS International Surveys.  These complement the previously released English language survey.  There are both language-specific and some country-specific surveys.  If you use VSTS in one of the languages and/or countries below, it would be helpful to us for you to take the survey and let us know your opinion.

    Japanese = http://c2.microsoft.fr/surveyIntlVSTS/?elng=1041

    Simplified Chinese = http://c2.microsoft.fr/surveyIntlVSTS/?elng=2052

    Traditional Chinese = http://c2.microsoft.fr/surveyIntlVSTS/?elng=1028

    Korean = http://c2.microsoft.fr/surveyIntlVSTS/?elng=1042

    German = http://c2.microsoft.fr/surveyIntlVSTS/?elng=1031

    French = http://c2.microsoft.fr/surveyIntlVSTS/?elng=1036

    Spanish = http://c2.microsoft.fr/surveyIntlVSTS/?elng=1034

    Italian = http://c2.microsoft.fr/surveyIntlVSTS/?elng=1040

    These are in English but specific for some countries.

    Middle East (in English) = http://c2.microsoft.fr/surveyIntlVSTS/?elng=1033

    Brazil (in English) = http://c2.microsoft.fr/surveyIntlVSTS/?elng=2057&src=Bra

    India (in English) = http://c2.microsoft.fr/surveyIntlVSTS/?elng=2057&src=India

    Malaysia (in English) = http://c2.microsoft.fr/surveyIntlVSTS/?elng=2057&src=Malaysia

    Indonesia (in English) = http://c2.microsoft.fr/surveyIntlVSTS/?elng=2057&src=Indonesia

    General English one (for any other country) = http://c2.microsoft.fr/surveyIntlVSTS/?elng=2057

    tags: ,

Page 1 of 1 (11 items)