|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
Developing Managed Code Form Templates Using the InfoPath 2003 Object Model
Microsoft Office InfoPath 2007 continues to support form template projects created with Microsoft Office InfoPath 2003 Toolkit for Visual Studio .NET or with Visual Studio 2005 Tools for the Microsoft Office System that have business logic written against members of the Microsoft.Office.Interop.InfoPath.SemiTrust namespace. Additionally, you can create a new form template project with managed code business logic that works against this InfoPath 2003-compatible object model to retain backward compatibility for users of InfoPath 2003. The 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.
Although creating business logic with the managed-code object model provided by the Microsoft.Office.Interop.InfoPath.SemiTrust namespace is still supported by Office InfoPath 2007, business logic written using this object model it is not supported for browser-enabled form templates deployed to Microsoft Office Forms Server 2007 or Microsoft Office SharePoint Server 2007 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 on creating form templates with business logic written with members of the Microsoft.Office.InfoPath namespace, see Developing InfoPath Managed Code Form Templates.
Also note that users of form templates compiled with Microsoft Visual Studio Tools for Applications (VSTA), Visual Studio 2005 with Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System, or Visual Studio 2008 with Visual Studio Tools for Office must have Microsoft .NET Framework 2.0 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 Managed Code Form Templates Using the InfoPath 2003 Object Model
Provides information on how to start creating managed code form templates that work with the InfoPath 2003-compatible object model.
- Creating Managed Code 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) 5.0 from InfoPath managed-code solutions.
- Security in InfoPath Managed Code Form Templates
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 Managed Code 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.