If you know you will use code behind in your InfoPath form you’ll have to publish it as approved form and upload it in the Central Administration (CA) of SharePoint. Normally you would publish your form, send it to your Administrator who uploads your form using the wizard. That’s ok, it works. There is nothing to complain about it.
But if you use your InfoPath form as one part of a bigger application which should run on SharePoint, it might be easier to put this form also into your Visual Studio solution. It’s easier for deploying at staging / test and production systems. And let me tell you, yes it is possible to publish your InfoPath form via a Visual Studio solution to CA of SharePoint.
All you have to do is follow these six steps. You will see, doing it this way produces one .wsp package which contains all your necessary items (e.g. Lists definitions, Content Types, Application pages, etc.) and can be deployed at the desired server. Please notice that i won’t show this for forms used for workflows in this post. But maybe i will do a post about it soon.
Step 1: Publish your InfoPath form
If you publish your InfoPath form (File – Publishing) there is a wizard which guides you through.
1. Add the SharePoint Server Url
2. Activate the checkbox to make it browser enabled and administrator approved.
3. Where to save the .xsn form file
Step 2: Add a module to your Visual Studio project and call it CustomForms
You can call the module like you want, but i called it CustomForms. After adding you can delete the sample.txt file. With “Add existing item” you add your published InfoPath form (.xsn file) into this module.
Step 3: Customize the Elements.xml file of the module
Important tags are Url, RootWebOnly, and the Type.
< ?xml version="1.0" encoding="utf-8"?> <elements xmlns="http://schemas.microsoft.com/sharepoint/"> <module Name="CustomForms" Url="FormServerTemplates" RootWebOnly="TRUE" > <file Path="IncidentReportingDetails.xsn" Url="IncidentReportingDetails.xsn" Type="GhostableInLibrary" /> </module> </elements>
Really important is the Type=”GhostableInLibrary” part, cause if you don’t set it, you can deploy your form, but it won’t work. Cause SharePoint creates a library at your Site Collection called FormServerTemplates in which the activated form .xsn file is uploaded as ressource.
Step 4: Add a Feature to your project
In order to activate the form correctly we also need a feature. Do not use a feature which might be already in your solution. Just add a new feature. It is better, to order your solution and cause of the changes coming soon. Set the Scope to Site. Your feature XML file should be similiar to this one:
<feature xmlns="http://schemas.microsoft.com/sharepoint/" Scope="Site" Title="Your Title" Description="your Description" Id="5acba068-8ceb-4cb4-b882-e112ef7b998f" ReceiverAssembly="Microsoft.Office.InfoPath.Server, Version=184.108.40.206, Culture=neutral, PublicKeyToken=71e9bce111e9429c" ReceiverClass="Microsoft.Office.InfoPath.Server.Administration.XsnFeatureReceiver"> <activationdependencies> <activationdependency FeatureTitle=" SharePoint Server Enterprise Site Collection features " FeatureDescription=" SharePoint Server Enterprise Site Collection features " FeatureId="8581a8a7-cf16-4770-ac54-260265ddb0b2" /> </activationdependencies> <elementmanifests> <elementmanifest Location="CustomForms\Elements.xml" /> <elementfile Location="IncidentReportingDetails.xsn" /> </elementmanifests> </feature>
As you can see you have to insert a ReceiverAssembly and a Receiver Class. These are important for the forms services. I add also an activation dependency. That means that at deployment time, it will check if the SharePoint Server Enterprise Site Collection feature is activated. If not, it cannot activate your solution. It is necessary to have this feature activated at site collection level.
Step 6: Deploy the project
That should it be. Now you should see your InfoPath form is available at Central Administration.
You should be able to open the form with the hyperlink:
Replace the red marked text with your values. Hope this helps you at any time.
..:: I LIKE SHAREPOINT ::..The article or information provided here represents completely my own personal view & thought. It is recommended to test the content or scripts of the site in the lab, before making use in the production environment & use it completely at your own risk. The articles, scripts, suggestions or tricks published on the site are provided AS-IS with no warranties or guarantees and confers no rights.
He is Consultant for SharePoint Solutions for collaboration, communication and business processes. He provides his customers applications based on standard features as well as development or combining the power of several microsoft tools like Dynamics CRM. In his free time he tries to collect tipps and worthy experience in this blog.