![]() Design a Form Template. If you want to design a form template that can be opened and filled out in either Microsoft Office InfoPath or a Web browser. This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn more Dev Center. Office UI Fabric Microsoft Graph Better with Office Word Excel Powerpoint Access Project OneDrive OneNote Outlook. Last modified: June 28, 2011 Applies to: InfoPath 2013| InfoPath Forms Services| Office 2013| SharePoint Server 2013 If you created an InfoPath 2003 managed code form template using one of the InfoPath 2003 Toolkits for Visual Studio and want to maintain compatibility with InfoPath 2003, you can continue to work on and further develop your form template project by opening it in Microsoft InfoPath and Visual Studio 2012. Alternatively, you can migrate and upgrade the code in your InfoPath 2003 project to use the new.NET object model provided by the namespace. When doing so, all of your code will need to be re-written to use members of the Microsoft.Office.InfoPath namespace, but all of the code from your previous project is retained and surrounded by #if InfoPathManagedObjectModel and #endif (C#) or #If InfoPathManagedObject Model and #End If (Visual Basic) statements for your reference. The following procedures describe how to open a managed code form template created by using the InfoPath Toolkit and maintain compatibility with InfoPath 2003 or migrate and upgrade to the new InfoPath object model. Open a managed code form template created with the InfoPath Toolkit and maintain compatibility with InfoPath 2003 using Visual Studio Tools for Applications. • Open the InfoPath Designer, and then click Open on the File tab. • In the Open in Design Mode dialog box, navigate to the project folder where the InfoPath Toolkit form template project is saved. By default, this will be a folder in C: Users username Documents Visual Studio Projects on the computer where the project was created. Or, you can move the folder to the location where InfoPath stores Visual Studio 2012 projects, which by default is C: Users username Documents InfoPath Projects • Click the file that is named manifest.xsf, and then click Open. ![]() • On the Developer tab, click Code Editor. • The message 'This form template must be saved before you can add Visual Basic or C# code to it' is displayed. Click OK to continue. • Navigate to the location where you want to save the file, name the file, and then click Save. • The message 'This code was created with one of the InfoPath 2003 Toolkits for Microsoft Visual Studio. InfoPath needs to migrate the toolkit project to a new format' is displayed. Click OK to continue. • Select the Visual Studio Solution (.sln) file for the project, and then click Open. • The message 'Your project has been migrated' is displayed when the migration process is complete. Click OK to continue. • The message 'The code in this form uses the InfoPath 2003 object model' is displayed with the prompt 'Do you want to upgrade your code to use the Microsoft Office InfoPath object model?' Click No to retain compatibility with InfoPath 2003 and to continue working with the object model provided by the namespace. For information about how to work with managed code form templates that are compatible with InfoPath 2003, see. Open a managed code form template created with the InfoPath Toolkit and upgrade it to use the new InfoPath object model using Visual Studio Tools for Applications. • Open the InfoPath Designer, and then click Open on the File tab. • Under Open a form template, click On My Computer. • In the Open in Design Mode dialog box, navigate to the project folder where the InfoPath Toolkit form template project is saved. By default this will be a folder in C: Users username Documents Visual Studio Projects on the computer where the project was created. Or, you can move the folder to the location where InfoPath stores Visual Studio 2012 projects, which by default is C: Users username Documents InfoPath Projects • Click the file that is named manifest.xsf, and then click Open. ![]() ![]() ![]() • On the Developer tab, click Code Editor. • The message 'This form template must be saved before you can add Visual Basic or C# code to it' is displayed. Click OK to continue. • Navigate to the location where you want to save the file, name the file, and then click Save. • The message 'This code was created with one of the InfoPath 2003 Toolkits for Microsoft Visual Studio. InfoPath needs to migrate the toolkit project to a new format' is displayed. Click OK to continue. • Select the Visual Studio Solution (.sln) file for the project, and then click Open. • The message 'Your project has been migrated' is displayed when the migration process is complete. Click OK to continue. • The message 'The code in this form uses the InfoPath 2003 object model' is displayed with the prompt 'Do you want to upgrade your code to use the Microsoft Office InfoPath object model?' Click Yes to upgrade the form template to use the new managed code object model provided by the namespace. Your form code is opened in the Visual Studio 2012 code editor with all of the code from your previous project surrounded by #if InfoPathManagedObjectModel and #endif (C#) or #If InfoPathManagedObjectModel and #End If (Visual Basic) statements for your reference. All of this code will have to be re-written to use members of the object model provided by the Microsoft.Office.InfoPath namespace. For information about how to work with managed code form templates that use the new InfoPath managed code object model, see. Microsoft Office InfoPath Help Conceptual and procedural information on designing form templates with InfoPath. To access Microsoft Office InfoPath Help, click the Help button in Microsoft InfoPath. When you are connected to the Internet, additional content and updated help topics are integrated into Help from the Microsoft Office Online Web site. This Web site contains white papers, sample forms, tools, articles, and information about developing InfoPath form templates. Microsoft SharePoint Server 2010 Software Developers Kit (SDK) Conceptual, procedural, and programming information for developers working with InfoPath Forms Services that is included as part of Microsoft SharePoint Server 2010. For more information, see the. This Web site contains information about using programs in the Microsoft Office System as a development platform. This Web site contains information about a variety of Microsoft development platforms and tools. This Web site contains information about developing programs and services that use XML. This Web site contains information about developing programs and services that use the.NET Framework. This Web site contains information about InfoPath, such as Knowledge Base articles, provided by Microsoft Support Services.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
April 2018
Categories |