Assign Work Item to multiple TFS Users part. II

At this point we have customized the work item to allow asignments to

To view tasks assigned to SXD_Group you need to update the "View Query" for your Work Items.

1- Right Click "My Work Items"

2- Select "View Query"

3- Add a new clause: "Or" - "Assigned To" - "=" - "SXD_Group"

4- Close and Save

enjoy !

Assign Work Item to multiple TFS Users part. I

It is possible to assign an existent work item to multiple TFS users.

In this case I'm going to explain how to assign an existent work item to multiple TFS users but keep in mind that you can also create a new work item from scratch to accomplish this.

For this example we're going to use the following variables:

TFSServer: http://tfsserver:8080/
ProjectName: ProjectMX
WorkItem: task (to customize)

How to do it:

1- Create a i.e. MX_Group within the TFS project.
2- Add users to MX_Group group
3- Customize the task Work Item:

- Using the VS 2005 Command Prompt export the task Work Item :
witexport /f OutputXMLDef /t TFSServer /p ProjectName /n WorkItem

witexport /f "D:\Temp\Task.xml" /t "http://tfsserver:8080/" /p "ProjectMX" /n task

- Change the following in the exported Work Item definition:
















- Save the definition and import it back into TFS :
witimport /f XMLDef /t TFSServer /p ProjectName

witimport /f "D:\Temp\Task.xml" /t "http://tfsserver:8080/" /p "ProjectMX"

4- After restarting Visual Studio 2005 you should be able to assign tasks to MX_Group.

Cannot create TFS Project Sharepoint Site after WSS 3.0 Upgrade

In my Test Environment, after upgrading to TFS 2008 and WSS 2.0 to WSS 3.0 an issue raised.
No team project could be created. I was pretty sure that the problem resided in the TFS - WSS mappings.

WSS 3.0 upgrade gets configured by default using the TFS server name (NETBIOS name MyTestTFS in my case). Many test environments use the NETBIOS name and this is something to take into account if you plan to move it into production in some point.

Here's the deal. I first created the complete update command for Sharepoint knowing that just the Admin site needs to be changed…but just in case:

TFSAdminUtil configureconnections /SharepointURI:http://MyTestTFS.csystems.com.ar:80 /SharepointSitesUri:http://MyTestTFS.csystems.com.ar:80/sites /SharepointAdminUri:http://MyTestTFS.csystems.com.ar:17013 /SharepointUnc:\\MyTestTFS.csystems.com.ar\sites

Nothing fixed at this point and now unable to create the Project Sharepoint site when creating the Team Project. A different error raised.
So I went to the WSS Local Administration site and checked the mapped sites to find that http://mytesttfs.csystems.com.ar/ was not there. So I added it as alternate internal URL.

EVERYTHING WORKS ! Now TFS and Sharepoint are correctly mapped allowing Team Projects creation using the TFS Server frinendly name.

TFS 2008 Build, the major improvement

What's new in TFS 2008 ?

Besides the performance, scale, Workspace mapping and the many UI improvements, TFS 2008 brings some new features mostly for Team Build.
It provides Continuous Integration and Scheduled Builds out of the box, Multi-Threaded and Incremental Builds.

Builds can be created, updated, stopped and deleted easily using the improved UI. You can also integrate Team build with existing build systems like Nant, Ant, make, etc.

The following chart displays Team Build compatibility between TSF 2005 and TFS 2008 versions.

In addition to that both TeamExplorer can be installed in VSTS 2005, only VSTE 2008 will allow you to access all TeamBuild functionalities within TFS 2008.

GUI tool for VssConverter

Well, there's a UI for Vss to TFS convertion available now.

I haven't tested it yet, but it seems worthy to try...Those who are interested can get it from here.

VSS to TFS Source Control migration

Team Foundation Server (commonly abbreviated TFS) is a Microsoft offering for source control, data collection, reporting, and project tracking, intended for collaborative software development projects. It is available either as stand-alone software, or as the server side backend platform for Visual Studio Team System(VSTS).

As Visual Source Safe is targeted towards individual developers or small teams with lightweight SCM needs, Microsoft is encouraging everyone else to migrate to the more sophisticated Team Foundation system.

There's a command line tool provided by TFS 2005 to migrate from VSS to TFS and is called VssConverter . The VSSConverter.exe is located in :\Program Files\Microsoft Visual Studio 8\Common7\IDE and is also available through the Visual Studio 2005 Command Prompt.

Due differences between this two technologies VSS historical information cannot be migrated. Basically, TFS source control does not support Sharing and Pinning. Because of this, Sharing, Branching (Sharing is a pre-condition of Branching) and Pinning historical information is lost when migrating to TFS source control.

Also, time stamps and source control bindings are not migrated.

Despite this limitations VssConverter.exe does a great job but it requires a lot of XML configuration.

The VSS Converter requires Microsoft Visual SourceSafe 2005 or a later version to run.

Want TFS 2005 to support WSS 3.0 ?

As you may know, TFS 2005 release relies on Sharepoint Services 2.0 for team site integration among other things.
I was looking for a way to allow my TFS 2005 to support WSS 3.0 since this new release has enhanced integration and new features.

Interested in WSS 3.0 ? here you can learn about what it brings to us.

There's a way to achieve this upgrade by applying a hotfix to TFS, but some prior steps have to be made.

All information is available here.