Getting Started Developing Form Templates Using the InfoPath 2003 Object Model

Office 2013 and later

Last modified: August 09, 2012

Applies to: InfoPath 2013 | InfoPath Forms Services | Office 2013 | SharePoint Server 2013

This section provides information on how to get started creating managed-code form templates that work with the InfoPath 2003-compatible object model provided by members of the Microsoft.Office.Interop.InfoPath.SemiTrust namespace.

In this section

How to: Create a Form Template Using the InfoPath 2003 Object Model: Provides information and steps for creating form templates that contain business logic that works with the InfoPath 2003-compatible object model.
Walkthrough: Creating and Debugging a Basic Form Template Using the InfoPath 2003 Object Model: A step-by-step guide that provides an introduction to creating and deploying a basic InfoPath form template that works with the InfoPath 2003-compatible object model.
Common Tasks for Developing Form Templates Using the InfoPath 2003 Object Model: Helps you quickly find the answers to common questions about developing form templates with business logic that works against the InfoPath 2003-compatible object model.
How to: Use Microsoft.Office.Interop.InfoPath.SemiTrust Members That Are Not Compatible with InfoPath 2003: Discusses how to work with new object model members that were added to the Microsoft.Office.Interop.InfoPath.SemiTrust namespace in Office InfoPath 2007 and InfoPath 2010.

Related sections

Creating Form Templates Using the InfoPath 2003 Object Model: Discusses initialization and clean-up code, how to add event handlers, how to debug and deploy InfoPath form templates that use the InfoPath 2003-compatible object model, threading support, and working with Microsoft XML Core Services (MSXML).
Understanding the InfoPath 2003 Object Model: Discusses the InfoPath 2003-compatible object model, and describes common programming tasks.
Troubleshooting Form Templates That Use the InfoPath 2003 Object Model: Contains tips for solving common problems that you might encounter when developing form templates that work with the InfoPath 2003-compatible object model.