Developing Form Templates Using the InfoPath 2003 Object Model
Applies to: InfoPath 2010 | InfoPath Forms Services | Office 2010 | SharePoint Server 2010 | Visual Studio | Visual Studio Tools for Microsoft Office
Microsoft InfoPath 2010 continues to support form template projects created with Microsoft Office InfoPath 2003 Toolkit for Visual Studio .NET or Visual Studio 2005 Tools for the Microsoft Office System that have business logic written against members of the Microsoft.Office.Interop.InfoPath.SemiTrust namespace. The topics in this section refer to the types and members of this namespace as the InfoPath 2003-compatible object model or simply the InfoPath 2003 object model. InfoPath 2010 also supports form template projects created with Microsoft Office InfoPath 2007 that use the InfoPath 2003-compatible object model. In addition, you can use InfoPath 2010 to create new form template projects that use InfoPath 2003-compatible object model to retain backward compatibility for users of Office InfoPath 2007. All topics in this section are specific to creating and developing form templates that work with the InfoPath 2003-compatible object model provided by the Microsoft.Office.Interop.InfoPath.SemiTrust namespace.
Important
Although creating business logic with the managed-code object model provided by the Microsoft.Office.Interop.InfoPath.SemiTrust namespace is still supported by InfoPath 2010, business logic written using this object model it is not supported for browser-enabled form templates deployed to Microsoft SharePoint Server 2010 with InfoPath Forms Services. Browser-enabled form templates must use the new InfoPath managed code object model provided by members of the Microsoft.Office.InfoPath namespace for custom business logic. For more information about creating form templates with business logic written with members of the Microsoft.Office.InfoPath namespace, see Developing InfoPath Form Templates with Code.
Also, note that users of form templates compiled with Microsoft Visual Studio Tools for Applications must have Microsoft .NET Framework 2.0 or later installed on their computers. Users of form templates compiled with Visual Studio .NET 2003 are only required to have Microsoft .NET Framework 1.1 on their computers.
In This Section
Getting Started Developing Form Templates Using the InfoPath 2003 Object Model
Provides information about how to start creating managed code form templates that work with the InfoPath 2003-compatible object model.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 managed-code form templates, threading support, and working with Microsoft XML Core Services (MSXML) from InfoPath managed-code solutions.Security in InfoPath Form Templates with Code
Discusses the security model for InfoPath form templates that use managed code, debugging fully-trusted InfoPath form templates, and related security procedures.Understanding the InfoPath 2003 Object Model
Discusses the InfoPath 2003-compatible object model, and common programming tasks for managed code form templates that work with that object model.Troubleshooting Form Templates That Use the InfoPath 2003 Object Model
Contains tips for solving common problems that you might encounter when creating managed-code form templates that work with the InfoPath 2003-compatible object model.
Related Sections
InfoPath Developer Portal
Contains links to technical articles, code samples, downloads, support, and other MSDN documentation on building custom InfoPath solutions.Microsoft Office Developer Center
Contains links to technical articles, code samples, downloads, support, and other MSDN documentation on building custom Office solutions.