Buck Hodges

Visual Studio Online, Team Foundation Server, MSDN

November, 2007

  • Buck Hodges

    Team System Web Access 2008 Power Tool is now available


    Today we have released the final version of the Team System Web Access (TSWA) 2008 power tool!  Team System Web Access provides a web interface to Team Foundation Server 2008.

    Here's a list of feature changes.  Of course, we also fixed a number of bugs.

    • New direct links: Previously, you could construct a direct link to a work item (http://mytfs:8090/wi.aspx?id=123).  Now you can also construct direct links to more features, and the direct links no longer open the main TSWA page, making them more responsive.  Keep reading to find out how to use them.
    • Performance improvements: The code now uses server memory more efficiently, resulting in increased performance.
    • Custom work item controls: First introduced in the CTP, we have continued to refine support for custom work item controls in TSWA.  To take advantage of this feature, you'll need to implement web versions of your existing custom controls.  You'll find documentation for it in the SDK folder underneath the folder where you install TSWA.  The following examples have been added since the CTP, in addition to the samples for checkbox, a work item picker, and a multi-value selector.
      • How to validate a work item on the client-side (Javascript)
      • How to validate a work item on the server-side
      • How to design a control whose field depends on the values of other fields
      • How to design a control that changes other field values (such as the WI state) and saves the work item
    • Team Build 2008 support: Also introduced in the CTP, you can view the build queue and queue new builds, which are features that are new for TFS 2008.

    For those of you who remember the need for the TSWA users group in the installation of the TSWA 2005 power tool, you'll be happy to know that is gone.  That was something we had to add to satisfy security requirements, but we've since changed the code to handle the impersonation better such that impersonated user identities no longer need access to any of the local directories for cache files and user settings (i.e., the code reverts to the service account while it accesses those).

    Note that you need to install Team Explorer 2008 on the computer before installing TSWA 2008.

    Direct Links

    Here is the list of direct links and examples showing how to construct them.  The previous releases only supported direct links to work items, and Neno Loje has a great post on how to modify work item alert emails to use TSWA links.  The new direct links, such as diff, provide the ability to make the checkin email alerts really useful, too (more on that later).

    • Work item tracking
      • Work item editor
        • Open the existing work item with ID 1234: http://mytfs:8090/wi.aspx?id=1234 
        • Create a new work item of type Bug in team project TeamProject:  http://mytfs:8090/wi.aspx?pname=TeamProject&wit=Bug
        • Create a new work item of type Bug in team project TeamProject and link it to work items 1234 and 5678: http://mytfs:8090/wi.aspx?pname=TeamProject&wit=Bug&workitems=1234,5678
      • Query editor
        • Open the query editor to create a new query: http://mytfs:8090/qe.aspx?pname=TeamProject
        • Edit the existing public query (under "Team Queries") called "Team Bugs" (scope is either public or private, which corresponds to Team Queries or My Queries, respectively, in English systems): http://mytfs:8090/qe.aspx?pname=TeamProject&name=Team%30Bugs&scope=public
      • Query results
        • Execute the private query (under "My Queries") called "My Bugs": http://mytfs:8090/q.aspx?pname=TeamProject&name=My%30Bugs&scope=private
    • Version Control
      • Changeset details
        • Display the details for changeset 1234 by specifying the changeset number: http://mytfs:8090/cs.aspx?cs=1234
        • Display the details for changeset 1234 by specifying the artifact URI: http://mytfs:8090/cs.aspx?csuri=vstfs:///VersionControl/Changeset/1234
      • Shelveset details
        • Display the details for the shelveset MyChanges by specifying the shevleset name and owner separated by a semicolon:  http://mytfs:8090/ss.aspx?ss=MyChanges;domain\UserName
      • History
        • Display the version history of the file or folder identified by item ID 789: http://mytfs:8090/history.aspx?item=789
        • Display the version history of the file $/TeamProject/Secret/foo.cs (specify del=N where N is the deletion ID if the file is deleted): http://mytfs:8090/history.aspx?path=$/TeamProject/Secret/foo.cs 
        • Display the version history of the directory tree at $/TeamProject/Secret (history of a folder is recursive; specify del=N where N is the deletion ID if the folder is deleted): http://mytfs:8090/history.aspx?path=$/TeamProject/Secret 
      • Compare files (diff)
        • Display the differences between the latest version of two different files, identified by item IDs 789 and 3456 ("o" indicates the original version that will be displayed on the left, and "m" indicates the modified version that will be displayed on the right): http://mytfs:8090/diff.aspx?oitem=789&mitem=3456
        • Display the differences between two different versions of the same file, identified by item ID 789 and changesets 100 and 200: http://mytfs:8090/diff.aspx?oitem=789&ocs=100&mitem=789&mcs=200
        • Display the differences between the latest version of two different files, identified by path (specify del=N where N is the deletion ID if the file is deleted): http://mytfs:8090/diff.aspx?opath=$/TeamProject/Secret/foo.cs&mpath=$/TeamProject/SecretBranch/foo.cs 
        • Display the differences between two different versions of the same file, identified by path and changesets 100 and 200 (add the appropriate deletion ID, odel=N or mdel=M, for deleted files): http://mytfs:8090/diff.aspx?opath=$/TeamProject/Secret/foo.cs&ocs=100&mpath=$/TeamProject/SecretBranch/foo.cs&mcs=200
      • View file
        • View the contents of the file identified by the item ID 789: http://mytfs:8090/view.aspx?item=789
        • View the contents of the file $/TeamProject/Secret/foo.cs (specify del=N where N is the deletion ID if the file is deleted): http://mytfs:8090/view.aspx?path=$/TeamProject/Secret/foo.cs
      • Annotate (blame)
        • Display an annotated view of file $/TeamProject/Main/foo.cs (specify del=N where N is the deletion ID if the file is deleted): http://mytfs:8090/ann.aspx?path=$/TeamProject/Main/foo.cs
        • Display an annotated view of file $/TeamProject/Main/foo.cs up until changeset 123 (specify del=N where N is the deletion ID if the file is deleted): http://mytfs:8090/ann.aspx?path=$/TeamProject/Main/foo.cs&cs=123
        • Display an annotated view of file identified by item ID 789: http://mytfs:8090/ann.aspx?item=789
        • Display an annotated view of file identified by item ID 789 up until changeset 123: http://mytfs:8090/ann.aspx?item=789&cs=123

    I've started a series of posts called TSWA Tips to help folks get the most out of Team System Web Access.


    [Update 6/14/2008]  The latest version of the TSWA power tool supports viewing shelvesets, so I've added the shortcut link for that.

    [Update 2/06/2009]  Added a new work item URL that will link the newly created work item to the specified work items.

  • Buck Hodges

    Building VS 2008 projects with TFS 2005


    The question has come up a couple of times as to how to get a TFS 2005 build agent (the build agent is the service running on the computer) to build a Visual Studio 2008 solution.  When you try to do it, you get the following error.

    Solution file error MSB5014: File format version is not recognized.  MSBuild can only read solution files between versions 7.0 and 9.0, inclusive.

    The TFS 2005 build agent finds msbuild.exe by asking the common language runtime (CLR) for its installing directory.  In VS 2008, the .NET framework version is 3.5, but the CLR remains at 2.0.  The result is that the code in TFS 2005 always finds msbuild.exe in the 2.0 .NET framework directory.  Since msbuild 2.0 does not recognize the version number in VS 2008 solution files, which was changed to 10.0, it produces the error message shown above.

    The TFS 2008 build agent will not work with a TFS 2005 server (application tier) because the communication protocol and the information required to run the build changed quite a bit.  As a result, you can't use a TFS 2005 server together with a TFS 2008 build agent.  We've actually included a setting in the TFS 2008 build agent that allows you to specify the path to msbuild.exe to deal with this issue in the future.

    I'll start by saying that I think the best "workaround" is to upgrade to TFS 2008.  There are lots of good reasons to do it, including lots of new features, performance improvements across the product, and a lot of bug fixes.  TFS 2008 is a significant improvement over TFS 2005 in all respects.  Having said that, I know not everyone is going to upgrade their servers immediately.

    The best workaround that I've seen is to create a "shim" msbuild.exe in the .NET 2.0 directory that invokes the msbuild.exe in the .NET 3.5 directory.  Mitch Denny posted this approach and the code to go along with it.

    Building .NET 3.5 Applications with Team Build 2005

    What I needed to do was create a program called MSBuild.exe which I could drop in on top of the .NET 2.0 version of MSBuild that simply took the arguments passed to it and call the .NET 3.5 version of MSBuild. It ended up being about 25 lines of code in a single mainline.


    MSBuild 3.5 will also build Visual Studio 2005 solutions with the 2.0 toolset, so you should be able to build either VS 2005 or VS 2008 solutions with this workaround.

  • Buck Hodges

    Visual Studio Team System chat - December 5, 2007


    Join members of the Visual Studio Team System product group to discuss features available in Team Foundation Server, Team Suite, Architecture Edition, Development Edition, Database Edition, and Test Edition. Hopefully, there will be a fair amount of discussion around the newly release 2008 version.

    I'm planning to be in the first chat.

    There will be two chat sessions.  Note that I have posted the times in the Eastern US time zone.

  • Buck Hodges

    TSWA tip: Copy a bug to quickly file a new bug in an area related to the original


    Like Team Explorer, Team System Web Access does not support work item templates yet (though you can get a power tool work item template add-in for Team Explorer 2005 -- look for power tools for TFS 2008 in December).  However, you can use the "Create Copy of Work Item" feature to copy a work item that's similar to the one you want to file.  Then you only need to change the information that's different for the new bug and save it.

    To do this, click the triangle beside the work item you want to copy and choose "Create Copy of Work Item" from the popup menu.  This particular feature is not available from the Tools menu on the tool bar, unlike "Add Related Work Item" which shows up in both places.


    Clicking on "Create Copy of Work Item" will present you with a list of team projects.  The list of work item types are shown in the next menu when you click on a team project.


    Once you choose the work item type, the new work item will open in a new window with all of the fields filled in from the original work item (if you choose a different work item type than the original, only fields that appear in the original will be filled in for the new work item).  Change the fields that need to be different and save the work item to finish creating the new one.

    Previous tip: TSWA tip: Send an email with a work item or query results

  • Buck Hodges

    Using CruiseControl.NET to trigger CI builds in TFS 2005


    James Dawson previously posted a plugin for CruiseControl.NET that provided a continuous integration facility for TFS 2005, which I mentioned back in August.  He's now set up a CodePlex project for it: TFS TeamBuild Task for CruiseControl.NET.  You can get both the binaries and the source code from the CodePlex project.

    Continuous integration is now built into Team Build 2008.  However, for those who have to continue using TFS 2005 for a while, projects like this provide a way to fill the gaps.

  • Buck Hodges

    Martin Woodward's presentation on what's new in TFS 2008


    Martin Woodward has a posted a great set of slides from a presentation he did on what's new in TFS 2008.  After going through all of the features other than build, he spends more than half of the slides on the build features of TFS 2008 (aka Team Build).  I highly recommend taking a look at the slides, particularly if you haven't paid close attention to TFS 2008 up to this point.

    Team Foundation Server 2008 - What's New Talk

    Last night I had the pleasure of presenting to my local .NET User Group (NIMTUG) on what is new in Team Foundation Server 2008.  Interestingly, most of the audience where new to TFS completely so I also covered a bit of ground on what Team Foundation Server did and why - however most of the talk concentrated on the Team Build stuff new in TFS 2008 and I ran through the wallboard demo that I wrote for TechEd.


    One of the slides shows a condensed diagram of the new object model for build in TFS 2008.  I've copied it here (you may need to make your browser wider to see the whole thing).  It does a great job of highlighting the central parts.


  • Buck Hodges

    How to uninstall VS 2008 Beta 2 before installing the final version of VS 2008


    There have been a few questions about how to correctly uninstall all of VS 2008 Beta 2 in order to install the final version of VS 2008.  Scott Guthrie posted the steps for doing this earlier today.  A subset of this list would apply if you have installed Team Foundation Team Explorer 2008 Beta 2, rather than the full VS 2008 with Team Explorer.

    At the end he recommends rebooting after removing everything and before installing VS 2008.  From my experience, that's good advice.  The only thing additionally I've typically done after uninstalling a non-RTM build is to delete the VS 9.0 registry hives (HKLM and HKCU) and the VS 9.0 directory under "Program Files."  Of course, there are no guarantees with this, editing the registry may render your machine nonfunctional, etc., so be careful and back up your data.

    Steps to Uninstall VS 2008 Beta2 before installing the VS 2008 Final Release

    A few people have pointed out to me that there are other smaller setup packages that are optionally installed by Visual Studio 2008 Beta2 that you should also look to uninstall (it isn't always required to-do this - but it is best to always do this to be safe).  A complete list of these additional setup packages (along with uninstall instructions) can be found here

    Below is the complete list of potential Beta2 components to uninstall (as well as the recommended uninstall order of them):

  • Remove "MSDN Library for Visual Studio 2008 Beta"
  • Remove "Microsoft SQL Server Compact Edition 3.5"
  • Remove "Microsoft SQL Server Compact Edition 3.5 Design Tools"
  • Remove "Microsoft SQL Server Compact Edition 3.5 for Devices"
  • Remove "Microsoft Visual Studio Performance Collection Tools"
  • Remove "Windows Mobile 5.0 SDK R2 for Pocket PC"
  • Remove "Windows Mobile 5.0 SDK R2 for Smartphone"
  • Remove "Crystal Reports 2007"
  • Remove "Visual Studio Asset System"
  • Remove "Microsoft Visual Studio Web Authoring Component / Microsoft Web Designer Tools"
  • Remove "Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime"
  • Remove "Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime Language Pack" (non-English editions only)
  • Remove "Microsoft Visual Studio Tools for Office Runtime 3.0"
  • Remove "Microsoft Document Explorer"
  • Remove "Microsoft Document Explorer 2005 Language Pack" (non-English editions only)
  • Remove "Microsoft Device Emulator 3.0"
  • Remove "Microsoft .NET Compact Framework 3.5"
  • Remove "Microsoft .NET Compact Framework 2.0 SP1"
  • Remove ".NET Framework 2.0 SDK"
  • Remove "Microsoft Visual Studio Codename Orcas Remote Debugger"
  • Remove "Microsoft Visual Studio 64bit Prerequisites Beta" (64-bit platforms only)
  • Remove "Microsoft .NET Framework 3.5"
  • After you finish uninstalling any and all of the above items, I'd recommend rebooting prior to installing the final VS 2008 and .NET 3.5 release to make sure there is no setup state still on the machine.

    If you run into any problems with either installation or uninstall, please make sure to post in the Visual Studio 2008 Setup and Installation Forum on MSDN.

    Technorati tags: ,
  • Buck Hodges

    How would you prioritize features for MSBuild?


    Dan Moseley, a developer on the MSBuild team, wants to know how you would prioritize features for the next version of MSBuild by asking, How would you spend $100 on MSBuild?  The release of Visual Studio 2008 is imminent, which means the product teams are beginning to work on the future, and he posts about some of the features that they are considering.

    How would you spend $100 on MSBuild?

    We're currently planning for our next version (aka, "Dev10" - no code name this time) and subsequent releases. In that spirit, I'd like to do a quick poll of MSBuild aficionados to help us keep our "vision" for MSBuild aligned with yours, our customers.

    First, a caveat - while ideally I would like to rank the results and work down the list, the reality is that we have other constraints: although we are a separate build platform, our biggest customer by far is Visual Studio and its customers. There's a lot more Visual Studio users than direct MSBuild users, so when Visual Studio needs to add a feature that requires work on MSBuild, we have to help. Then there's other constraints, like team resources. There's no guarantee which of these will appear in what version, and some of them may not be worth any investment. Some of them I just made up.

    OK. Here’s some brainstormed features.


    This is a great opportunity to influence the future of MSBuild, so be sure to post your opinion.  I've posted my own take on this in the comments to Dan's post.

    Technorati tags:
  • Buck Hodges

    TSWA tip: Send an email with a work item or query results


    Let's say you're going through your bugs and want to ask someone a question about one of them.  You can use Team System Web Access to send that person an email containing all of the work item's information and a link to it.

    To email a work item, open the work item in TSWA.  Go to the Tools menu shown below and choose Send as Email.


    You'll get a new window where you can enter the person's full email address and type a message.  The message body contains a link to the work item in Team System Web Access and all of the work item's fields and contents.


    You can also email query results.  As with the work item above, go to the Tools menu and choose Send as Email.


    You'll then get a similar email window that contains the results of the query and a link so that the email recipient can run the same query.



  • Buck Hodges

    TSWA tip: Search bugs and reports


    [Update 10/6/2008]  In addition to the default search behavior described below, TSWA 2008 SP1 adds Outlook-style search capability, which is described here.

    Have you ever wanted a quick way to find the bugs containing some word?  Team System Web Access comes to your rescue.

    In the upper left corner underneath the team project selector, there is a search box.  Type in a word and hit Enter.  If you want to search for a phrase rather than a single word, simply enclose it in quotation marks (e.g., "team build" or "team foundation server").  Without the quotation marks, you'll be searching for all work items having all of those words (e.g., entering "team build" without quotation marks finds all work items containing both the word "team" and the word "build" rather than just the phrase "team build").

    Here I'm searching for all work items in the Orcas team project containing the word "tfsbuild" in either the title or the description.  This will find tfsbuild, tfsbuild.exe, tfsbuild.proj, etc.


    Here are the results.  In this case I've found 65 bugs.  Had there been any reports containing that word in the title or description, each would have been listed as well (e.g., we have 17 reports in Orcas containing the word "feature").

    In case you are thinking that it's only searching the titles, I've highlighted two work items below that don't have the term "tfsbuild" in the title but do contain it in the description field.



    [Update 11/9/07]  I've corrected the difference between searching for a phrase in quotation marks and a set of words in a work item.

    [Update 3/17/08]  I've clarified the text so that it's clear that only the title and description are included in the search in TSWA 2005 and 2008.

  • Buck Hodges

    Turning off Just-in-Time Debugging on your servers


    I saw Mac Noland's post tonight about turning off the just-in-time debugging popup window on his TFS server.  We've had this problem internally.  If you have a debugger installed on your computer, such as Visual Studio or WinDbg, the installation will enable just-in-time debugging such that when something crashes you'll get a window asking you whether you want to debug the problem.

    That's a great feature, except when there's no one around to dismiss the dialog.  If you have a build computer, for example, and someone's custom msbuild task crashes in the middle of the night, you'll probably just want the msbuild process to exit rather than hang the build.  It gets even worse if you connect to the computer via terminal services and don't connect to the console session, because you won't even see the dialog.  The same is true on your application tier as well.

    To turn off JIT debugging, you'll need to delete the two registry keys described in Visual Studio Debugger Just-In-Time Debugging.

  • Buck Hodges

    SharePoint lists in Outlook 2007 are awesome


    If you use Outlook 2007 and SharePoint, you really need to read this.  I've been using this feature for the last couple of weeks.  It syncs the documents into Outlook so they are available offline, you can search them, and you can edit and upload when you get back online.  It's really slick.  Read the post.

    SharePoint and Outlook – The Perfect Link

    Outlook 2003 introduced integration with SharePoint, allowing you to see some SharePoint information (like calendars) in Outlook alongside your personal information. In Outlook 2007, we made this a whole lot better.

    Here we’ll focus on the new Document Library syncing capability that allows you to easily access, preview, search, and edit your SharePoint document libraries in Outlook.


    Now if they would just give me the ability to sync my OneNote notebook through Outlook, I'd be all set!  Right now, I still use the feature where you can drop documents into Outlook and edit them anywhere.  I can't get to my shared OneNote notebook when I'm not on the corporate network.  They could call the feature OneNoteOut (or maybe OffNote).

    Technorati Tags: ,
  • Buck Hodges

    How to list the team projects created with a particular template in TFS 2008 or 2010


    This question came up on an internal discussion, and I thought the answer would be useful to post.


    How we can find the list of projects created with the a particular VSTF template in TFS 2008 or 2010? In TFS 2005 we can find out programmatically as well with the query but in the new version we are not able to do so.


    Sam Heald, a developer on the work item tracking server team, responded with the following answer.

    This information is no longer stored automatically in TFS 2008 and newer.

    In TFS 2005, a templateId was returned as an out parameter of the GetProjectProperties method on the ICommonStructureService interface.

    However, this templateId might not point to the same template used during project creation for that project (deleted/overwritten templates are purged, ids are re-used). Additionally, most project attributes initialized by the project creation wizard (aka PCW) can be customized or changed after the fact.

    In TFS 2008 or newer, the templateId parameter always returns -1.

    If you wish to simulate the old functionality, you can modify your process templates to put the template name in the generic project properties property bag. In the properties element in the classification.xml, you can define name-value pairs to be created at project creation time, e.g.:

    <property name="TemplateName" value="MSF Agile v4.0" />

    [UPDATE 2/26/2010] This post applies to TFS 2008 and TFS 2010 (and probably future releases).  I've updated the text to reflect that.

  • Buck Hodges

    Windows Live Writer 2008 is now available


    The first version of Windows Live Writer is now available.  I've been using the betas for a long time, and I think it's a great application (and it's free).  I use it to write all of my blog posts.  If it weren't for Live Writer, I wouldn't have written nearly so many blog posts.

    Windows Live Writer: Out of Beta

    Thank you to everyone who tried out the beta releases of Writer over the last year and gave us feedback. Over 1.5 million of you downloaded our last beta release, and your input helped make Writer the product it is today. 

    Our goal from the start has been to help make blogging more powerful, intuitive, and fun for everyone. Today, we’re proud to announce that Windows Live Writer 2008 is now available!

    Download Writer 2008
    Windows Live Writer 2008 (version 12.0.1366.1026)


    There are lots of great plugins for Live Writer as well.

    I use this one for doing syntax highlighting: Syntax Highlighter.

    At some point I'll have to try the Ink Blog Plugin on my tablet PC.

    I also like Mike Stall's Paste From Console that I finally got around to trying tonight.  I've tweaked the following parameters.

    ColorizeHtmlFormat:  <b><span style="color: rgb(0,0,160)">{0}</span></b><span style="color: rgb(164,0,0)">{1}</span>

    HtmlFormat:  <table bgcolor="dddddd" border=0><tr><td><pre>{0}</pre></td></tr></table>

    Here's what the output looks like.  I may have to play with the colors some more, but it's a good start.

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\Documents and Settings\Buck Hodges>dir
     Volume in drive C is PROGRAMS
     Volume Serial Number is 342D-79C3
     Directory of C:\Documents and Settings\Buck Hodges
    10/19/2007  06:30 PM    <DIR>          .
    10/19/2007  06:30 PM    <DIR>          ..
    07/04/2007  02:32 PM    <DIR>          .thumbnails
    12/19/2004  10:12 PM    <DIR>          Desktop
    03/02/2006  06:18 PM    <DIR>          My Documents
    09/23/2004  06:55 PM    <DIR>          Start Menu
    12/25/2003  04:48 PM    <DIR>          WINDOWS
                   6 File(s)        357,965 bytes
                   8 Dir(s)  42,552,401,920 bytes free
    C:\Documents and Settings\Buck Hodges>

    Mike has also written a series of posts on various aspects of how to write a plugin for Live Writer.

    Technorati tags:

  • Buck Hodges

    TSWA tip: Bulk edit


    Sara Ford has a Visual Studio Tip of the Day series going.  I thought I'd publish some tips on using Team System Web Access, and this is the first.  I don't think I'll be able to do a tip per day.  Calling it a "TSWA tip a few times a week" just doesn't sound that great.  So I'll just leave it as TSWA Tips.

    In the regular Team Explorer (aka Team Foundation Client), you can't edit work items in bulk except by exporting them to Excel (at least as of Team Explorer 2008).  However, you can do this using Team System Web Access.

    First, select the work items that you want to edit in bulk by clicking the checkbox beside each.  I've selected five bugs below.  Then, select Bulk Edit -> Edit Work Items from the drop down menu near the upper right hand corner (or upper middle, depending on how wide your window is).


    Now you are presented with a window where you can edit the core fields of a work item.  While this is not as flexible as defining the fields to edit like you can using a custom query and exporting to Excel, it's really convenient.

    Here they all have a State of Closed, and I'm changing all of the bugs to be assigned to Closed (they were previously assigned to me).  When you click Save, you will see the progress as each work item is updated.


    And I've just noticed that we didn't catch the fact that "successfully" is misspelled.  I'll file a bug on that. ;-)

  • Buck Hodges

    TFS 2008 ships this month


    Yesterday, Soma announced that VS 2008 and TFS 2008 ship this month.  Prior to that, we had only said it would ship by the end of this year.  It's going to be an exciting month.

    Not long after TFS 2008 ships, we're going to ship the final version of the Team System Web Access 2008 Power Tool, and it includes a few new features.  I'll write more on those later.

    Microsoft Commits to November Release Date for Visual Studio 2008 and the .NET Framework 3.5

    Microsoft expands interoperability options for partners, delivers new innovations with Microsoft Sync Framework and Popfly Explorer releases.

    BARCELONA, Spain — Nov. 5, 2007 — Today, during the keynote address at Microsoft TechEd Developers 2007, S. “Soma” Somasegar, corporate vice president of the Developer Division at Microsoft Corp., announced that Microsoft will release Visual Studio 2008 and the .NET Framework 3.5 by the end of November 2007. Visual Studio 2008 and the .NET Framework 3.5 enable developers at all levels to rapidly create connected applications that offer compelling user experiences for Windows Vista, Windows Server 2008, the 2007 Microsoft Office system, mobile devices and the Web.


    Technorati tags: ,
  • Buck Hodges

    TFSBuildLab 1.0 for TFS 2005


    I last mentioned TFSBuildLab back in August when it reached beta 2.  Peter Blomqvist and Mathias Olausson have now released 1.0.  For those of you who aren't going to move to TFS 2008 in the near future (it ships by the end of this year), you'll want to look into this.  I also posted a list of CI solutions for TFS 2005 about a year ago.

    TfsBuildLab v1.0 is out there !!!

    Finally we are feature complete as we intended it to be from the start (download it from here) we missed out intended deadline by almost 3 weeks :( (before 22/9) but for a sparetime project it still is decent... We have now been dog fooding TfsBuildLab in production since 2007-04-24 on a several projects the largest of them consisting of 5 parallel development branches each containing aproximately 10 000 source files.

    Some statistics since the start (didn't have the time to do the graphs this time):

    2998 Automatic cleanups
    1554 Scheduled builds
    1359 Continous integration builds

    What's new in version 1.0?

    * Automatic rescheduling when adding new scheduled trigger.
    * A report for displaying statistics from the triggers and retention policies.
    * Support for overriding build script parameters both for CI and queued builds.
    * Support for only deleting the build drops.
    * Support for configuring retention policies based on build quality.
    * Performance improvements by introducing caching

    Admin Client
    * Added feedback when delteing multiple builds.
    * Support for forcing recaching on the server.
    * Support for overriding build script parameters on queued builds.
    * Support for overriding build script parameters on triggers.
    * Added range paramters when listing log entries to limit the result data.

    Checkin Policies
    * Removed the need for TfsBuildLab when using the restricted paths policy.

    Build Task
    * New custom build task to use overloaded parameters (LoadOverriddenProperty)

    Technorati tags: tfs 2005, team foundation, team build, continuous integration, scheduled builds

Page 1 of 1 (17 items)