I got this strange litte error a while back when I tried to run a newly created build definition: “Value cannot be null. Parameter name: path1”. Not much to go on in that message…
My configuration is a Windows 7 x64 and VS 2010 Beta 2 Ultimate with TFS Basic running locally. Build controller and agent is also running locally. First I thought this was a problem related to my x64 OS. But after testing this on a different box running x86 and getting the same result that obviously wasn’t it.
So after getting some great help from the product team it turned out to be an issue with a registry value that was affected by the current regional settings for the decimal separator. In Sweden we use comma (,) instead of th US-default period (.) and that’s what caused this error to occur.
So to solve this problem you can simply change the regional settings for the build agent to use period instead of your normal symbol.
Another option is to use an updated build template xaml file, which can be found here.
Yesterday Microsoft announced the aquisition of Teamprise, the company providing access to TFS from other platforms and IDE. I think it’s great that Microsoft will provide a complete solution so hopefully this will make it even more natural to use TFS in an heterogenous development environment.
According to Mary-Jo Foley at ZDNet, the former Teamprise tools will be available as part of Visual Studio 2010 Ultimate or as a separate package;
New users will be able to buy Team Foundation Server plus Teamprise shipped as a single package. The bundle will be offered as part of Microsoft’s Visual Studio 2010 Ultimate SKU or at retail for approximately $799.
Reference: Microsoft ‘builds a branch to Java developers” with Teamprise buy
So, just look at this beautiful picture showing the equivalent of Team Explorer running on Mac OSX:
Read the full press-release here: Microsoft Acquires Teamprise Assets, Provides Cross-Platform Support for Visual Studio.
Have you ever created a work item type and later on wanted to change the name to something different? Then you know the pain this will result in… Add new type definition, migrate data from old type to new (yes, most of that done by hand since work item ids change and so on) and finally delete the old work item type. Ohhh…
Now with TFS 2010 it is possible to rename a work item type definition. Using the command-line tool witadmin.exe you can specify the renamewitd argument followed by the details about the work item type to rename: