General

Re: Contribute to InfoPath 2007 Developer docs

Mark Roberts — Fri, 09 Feb 2007 08:59:40 GMT

Because of the way we need to integrate into the Microsoft Scripting Editor for JScript/VBScript, and into VSTA for C#/Visual Basic, our docs are divided into two sets.

To get to the InfoPath Developer Reference, which contains general developer overviews, and script-specific procedures and reference:

Open the InfoPath designer and click Microsoft Office InfoPath Help on the Help menu.
By default and if you're connected to the Internet, this will access the help topics from the Office Online server. If you want to turn that off, in the lower right corner of the help viewer, click Connected to Office Online, and then click Show content only from this computer.
To switch to viewing the developer content, click Search, and then click Developer Reference.
If you don't see the Table of Contents, click the Show the Table of Contents button (the button with a book on it above the Search box).

To get to the InfoPath Developer Reference for Managed Code Form Templates, you first need to create a managed code project by creating a blank form, and then:

On the Tools menu, click Form Options.
In the Category list, click Programming, select either Visual Basic or C# from the Form template code language drop-down list, and then click OK.
Open VSTA by pointing to Programming on the Tools menu, and then clicking Visual Studio Tools for Applications.
Finally, click Help, and then click Contents.

Re: Contribute to InfoPath 2007 Developer docs

Patrick Halstead — Fri, 09 Feb 2007 07:14:17 GMT

Thanks for the quick reply. How does one get to the Developer Reference pieces from the designer? I found an xml file in one of the directories with a dll, but can't figure out how to access. Is this through Visual Studio?

Thanks again for the posts. This is very helpful.

Re: Contribute to InfoPath 2007 Developer docs

Mark Roberts — Fri, 09 Feb 2007 06:06:30 GMT

Yes, you do need to log in with a Windows Live ID (or Microsoft Passport if you already have that) to add comments to the online documentation.

We don't currently have plans to create .chm downloads, but I can look into that. All of this stuff will ultimately be part of the MSDN Library and can be installed locally if you have Visual Studio.

As I noted in my other post, the two "Developer Reference" pieces are available from the InfoPath form designer, and from the VSTA enviroment when you install InfoPath 2007.

Re: Contribute to InfoPath 2007 Developer docs

Patrick Halstead — Fri, 09 Feb 2007 05:49:31 GMT

Hi Mark,
Thanks for posting. I tried to add content but was asked for my Windows Live ID. Is this required to post? Seems a little bit of a high bar to require everyone to get a Windows Live Id. I guess it's kind of like asking for registration in a forum, but anyway, I really like the CHM files. Are those CHM files gone? Do we have to use online content? I like the speed and performance of the SDK that shipped in InfoPath 2003 as a CHM file. How can we download the content as a CHM file?
Regards,

Contribute to InfoPath 2007 Developer docs

Mark Roberts — Fri, 09 Feb 2007 05:25:23 GMT

All Office InfoPath 2007 developer documentation that is published online in the MSDN Library now supports the MSDN Community Content features that enable users to comment on, edit, and add content to online documentation.

On behalf of the InfoPath Developer Documentation team, I would like to encourage you use these features to provide feedback, add code examples, and other information that will be useful to other users of the documentation (worldwide!). To do so, click the Add new Community Content link, which is located under the Community Content heading at the bottom of each page, and then log in using your Windows Live ID or Microsoft Passport. For more information about using MSDN Community Content features, see the MSDN Community Content FAQ http://msdn2.microsoft.com/en-us/library/communitymsdnwikifaq.aspx).

The different reference components of the InfoPath 2007 Developer Documentation are located in the following areas of the MSDN web site:

New InfoPath 2007 Managed Code Object Model -
http://msdn2.microsoft.com/en-us/library/microsoft.office.infopath(vs.80).aspx

InfoPath 2003-Compatible Managed Code Object Model -
http://msdn2.microsoft.com/en-us/library/microsoft.office.interop.infopath.semitrust(vs.80).aspx

InfoPath Managed Code External Automation Object Model -
http://msdn2.microsoft.com/en-us/library/microsoft.office.interop.infopath(vs.80).aspx

COM and Scripting Object Model -
http://msdn2.microsoft.com/en-us/library/bb230016.aspx

Microsoft Office Forms Server 2007 Automation Object Model -
http://msdn2.microsoft.com/en-us/library/microsoft.office.infopath.server.administration.aspx

XmlFormView Control Object Model -
http://msdn2.microsoft.com/en-us/library/microsoft.office.infopath.server.controls.aspx

InfoPath 2007 XSF Schema Reference -
http://msdn.microsoft.com/en-us/library/bb265224.aspx

Note: In addition to the reference content listed above, all of the conceptual and procedural topics in our MSDN online documentation also support the MSDN Community Content features.

Thanks!