That is essentially the same as my code now. Since the InfoPath templates (.xsn) does not have content of type IProjectFileContent, they are not compiled, but they are opened. As far as I can tell all the fields are there in the package, so maybe there is something missing in the InfoPath forms? I will have to dig a bit deeper.

Cheers!

The code here is a bit old. this newer code might work better:
Project k2Proj = new Project();
k2Proj.Load(@”c:\testing\k2MsBuild\K2WorkflowProject1\K2WorkflowProject1\K2WorkflowProject1.k2proj”);

foreach (ProjectFile pf in k2Proj.GetAllFiles(true))
{
if (!pf.Excluded)
{
pf.Open();
IProjectFileContent so = (IProjectFileContent)pf.Content;

so.Compile();
}
}

LogLine(“Creating deployment package and adding environment.”);
DeploymentPackage depPackage = k2Proj.CreateDeploymentPackage();
AddEnvironment(depPackage); // Add the environment fields to the deployment package.

LogLine(“Saving deployment package”);
depPackage.Save(@”c:\testing\deploymentpackage\”, “runme”);

Please check if the adding of the deployment package is correct. You can also look in the msbuild file (it’s XML) to see if everything is added correctly.

I have built a TFS 2010 build Task which uses some of the code from your article. However, I have a problem with InfoPath forms (.xsn) files in the package. When I try to deploy them I get an error messge: “The SharePoint site URL is null”
This happens during the step:”Checking if Forms Services is installed”

Do you have any idea what could cause this?

regards,
Natrajk

We did not automate the deployment of the package. In our TFS2008 environment, that would require some batch of powershell scripting. We did not automate it because it wasn’t needed anymore, but should be pretty easy.
As for TFS2010, everything (especially the build process) is different and I don’t know how that works :(

regards,
Ruben