Using TFS for Source Control in InfoPath 2010

re: Using TFS for Source Control in InfoPath 2010

RKE — Fri, 24 Feb 2012 19:53:55 GMT

Philip & Christopher,

I found I wasn't able to save the XSF file even when the component files were not checked out and while Read-Only unchecked for all files. I've described the problem here where you might consider commenting:

social.msdn.microsoft.com/.../0f41e07d-1742-479b-ab64-0f8d614e37c2

re: Using TFS for Source Control in InfoPath 2010

Constructive criticism — Mon, 31 Jan 2011 03:50:59 GMT

One more thing, and I say this with all possible respect: The repetitive use of the phrase "go ahead" 20-30 times in a 10 minute video makes for an office-space metaphor that is borderline painful to watch to completion.

re: Using TFS for Source Control in InfoPath 2010

Constructive criticism — Mon, 31 Jan 2011 03:46:12 GMT

As others have already stated, I have discovered this break away from VS 2010 integration to be a major step backwards in infopath development. Using a separate application for editing form code poses some serious hassles when: a) you want to use .NET 3.5 features such as linq. b) Your form code is referencing code written in your other primary IDE. I was surprised to discover this limitation and spent the better part of a day trying to figure out how to create a new infopath form project in VS 2010.

re: Using TFS for Source Control in InfoPath 2010

Daniel — Tue, 21 Dec 2010 04:40:25 GMT

Do you have any timeline for Visual Studio 2010 integration? As VSTA is obviously going backward from VS 2008 in terms of IDE, source control, debugging and SharePoint integration. We might stick with Infopath 2007 till IFP 2010 supports VS integration.

re: Using TFS for Source Control in InfoPath 2010

Leland — Tue, 07 Dec 2010 20:44:12 GMT

In VS2008, we would have solutions that would typically have a SharePoint workflow project and then 1 or several projects that were InfoPath form projects that the workflow would use at various points in the flow. With the new way of doing things in seperate environments, how do you affect debugging? I need to be debugging the workflow and traverse into the code-behind in the InfoPath form. I am not understanding how to achieve this. Any help would be greatly appreciated.

re: Using TFS for Source Control in InfoPath 2010

Vythees — Fri, 08 Oct 2010 07:07:12 GMT

Thanks for the video, We are evaluating InfoPath as option for our document standardization review. It would be great if there is a straight forward & clear approach to integrate with source control system.

Also please let me know where I can find best practice guidelines for InfoPath development ( like versioning, source control,security, schema design, deployment).

re: Using TFS for Source Control in InfoPath 2010

Fernando — Sat, 14 Aug 2010 16:33:50 GMT

I figured out why...It's because I moved the folder where I exported the first time.

re: Using TFS for Source Control in InfoPath 2010

Fernando — Sat, 14 Aug 2010 15:10:05 GMT

Good article. I've a problem trying to save the xsf file, It only allow me to save as xsn file. Thanks.

re: Using TFS for Source Control in InfoPath 2010

Eugene Rosenfeld — Thu, 08 Jul 2010 20:36:05 GMT

Very sad about the lack of InfoPath development support in VS 2010. Are there any plans to release this support in a service or feature pack? I just can't see having our developers flip between 3 applications to incorporate InfoPath into our solution, especially since the functionality did exist (though somewhat buggy) in Office 2007 / VS 2008. It really makes me feel like InfoPath is just not ready for prime time.

re: Using TFS for Source Control in InfoPath 2010

infopath1 — Mon, 28 Jun 2010 19:15:07 GMT

This should still work. Have you tried reinstalling Office?