Eric lippert - Amazon Web Services

createteamproject /collection:http://ssgs-vs-tfs2012:8080/
tfs/DefaultCollection /teamproject:\”” + ProjectName + “\”
/processtemplate:\”MSF for CMMI Process Improvement 6.2
\””;
ProcessStartInfo psi =new ProcessStartInfo(“cmd.exe”);
psi.UseShellExecute = false;
psi.RedirectStandardOutput = true;
psi.RedirectStandardInput = true;
psi.RedirectStandardError = true;
psi.WorkingDirectory = @”C:\”;
psi.Verb = “runas”;
//start the process
Process p = Process.Start(psi);
p.StandardInput.WriteLine(args);
p.WaitForExit();
p.StandardInput.WriteLine(“EXIT”);
p.Close();
}
This workflow project is built and deployed to the SharePoint
server. After deployment, it is associated with the document library
that is hosting the Vision Document. It is configured to run when
a Vision document is created and then changed having the state
‘Approved’. This workflow will trigger the creation of a team
project. The name of that team project is provided by the approver
as property of the vision document in the SharePoint Library.
Now we will focus on another driving document – Requirement
Document. We create a document library in the team portal that
will provide a repository for requirement document for the project.
We will call that document library as ‘Requirement Documents’.
The requirement document is a standardized document in every
organization and its structure does not change much. We are going
to assume that it is the MS Excel worksheet that contains multiple
requirements, each individually on a row and the title of each
requirement is in column B.
For the document library, we will have a similar set of properties
that we had created earlier for the library that we had created for
Vision Document. We will have ‘Team Project Name’ and status as
two properties.
We will also create a SharePoint workflow that will have the event
handling code. In this code, we will read the requirement
document and create work items of the type Requirement. First we
should add a few references to the TFS API class libraries and their
related using statements. We are going to use OpenXML that is a
standard used for editing MS Office files
programmatically without installing MS Office, usually on the
server. We can download V 2.0 (one that I used) of that from http://
www.microsoft.com/en-in/download/details.aspxid=5124.
using Microsoft.TeamFoundation.Client;
using Microsoft.TeamFoundation.WorkItemTracking.Client;
The boilerplate code for such a SharePoint workflow project is as
follows:
private void CreateRequirements()
{
prj = (string)workflowProperties.Item[“Team
Project Name”];
collection = new
TfsTeamProjectCollection(new
Uri(“http://ssgsvs-tfs2012:8080/tfs/
DefaultCollection”));
store = collection.
GetService();
SPWeb web = workflowProperties.
Web;
SPFile file = web.
GetFile(@”http://
ssgs-vs-tfs2012/sites/
DefaultCollection/SSGS%20CMMI/
Requirements%20Documents/
RequirementDocument.xlsx”);
SPFileStream dataStream = (SPFileStream)file.
OpenBinaryStream();
SpreadsheetDocument document = SpreadsheetDocument.
Open(dataStream, false);
WorkbookPart workbookPart = document.WorkbookPart;
IEnumerable sheets = document.WorkbookPart.
Workbook.GetFirstChild().Elements();
DNcmagazine www.dotnetcurry.com | 33