______________________________________________
Nigel Shaw
(613) 692-0060 x 210 (off) • (613) 371-3942 (cell)

Exia Corp.
Developers of The Exia Process for Software Development Productivity
5390 West River, Suite 200, Ottawa, ON, Canada, K4M 1G4
Tel: (613) 692-0060
http://www.exiaprocess.com

This is great add-on for TFS 2010!
Are you going to implement CMMI process soon?
Our team has decided to use CMMI.
So if you can implement CMMI on this product, we will definitely use it.

Thanks,

Yukio

[TestMethod]
public void ClearWorkItemLinksTest()

at this line

bug1.Save();

do you know why, please?

Thanks for you attention.

It was a great help from you for the VSS 6.0 to TFS 2010 migration.

We are doing migration from VSS 6.0 to TFS 2010 using VSSconverter utility. When we start doing this we get an error.
“the vss converter requires visual sourcesafe 2005″
Is that mean, we can not direclty migrate from VSS 6.0 to TFS 2010?

I appreciate any help in this.

Regards,
Himanshu

///

[TestMethod]
public void CreateTeamQueryInRootFolderTest()
{
TfsApiInterface tfsApiInterface = new TfsApiInterface();
tfsApiInterface.CreateTeamQuery(project, “Exia Process”, “Requirements”, “SELECT System.ID, System.Title FROM WorkItems WHERE [System.TeamProject] = @project AND [System.WorkItemType] = ‘Document Element’ AND [ExiaProcess.ElementType] = ‘Requirement’”, “Requirements”);
}

Just for information sake, the reason we need this in our API is so that we can query our documentation. The Exia Process not only manages work items, it also manages all project documentation. To do this, we create one custom work item type, the DocumentElement type.