The general requirement is a “round-trip” of the form you want to add or replace. Before adding or replacing forms in a WSP, they need to be published. Once the form is in a WSP, it can be imported into any Visual Studio project (i.e. a project that defines a custom List definition) and reused. When you publish the form, URLs in the XSF file can be relativized, and other content can be added\/removed from XSN components as required by the publish process. We’re proposing the following, for example, when replacing a WSP form:<\/p>\n
1. Open the WSP in Visual Studio
\n2. Locate the XSN in the WSP (there is a standard structure for both list and form library forms).
\n3. Download a copy of the XSN from SharePoint server using SPD, or make a copy of the XSN that is currently in the WSP.
\n4. Make the required modifications to the XSN in the InfoPath Designer application
\n5. Publish the form back to SharePoint
\n6. Download the XSN from SharePoint using SPD.
\n7. Replace the XSN in the WSP
\n8. Repackage\/deploy the WSP<\/p>\n
That’s the general “life-cycle” and practice. The process below is touching on deploying a SharePoint list form:<\/p>\n
If you’ve already upsized a list, before importing the Site WSP into Visual Studio, the XSN will exist in the WSP and can be modified. There is also a process for adding a form to a list definition in a WSP which involves several manual steps. At a high level, the latter involves:<\/p>\n
1. Add the XmlDocument to the Schema.xml (under List instances)
\n2. Under the Modules node, add a new Module (Item_):<\/p>\n
3. Add the Item_pages Module:<\/p>\n
4. Add a property bag per item to the modules, one for each:<\/p>\n
On the “Features” node add the Modules created before (step 2 & 3: Lists<name>Item_\u00a0\u00a0 & Lists<name>Item_pages)<\/p>\n
That’s it!<\/p>\n","protected":false},"excerpt":{"rendered":"
The general requirement is a “round-trip” of the form you want to add or replace. Before adding or replacing forms in a WSP, they need to be published. Once the form is in a WSP, it can be imported into any Visual Studio project (i.e. a project that defines a custom List definition) and reused. […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-998","post","type-post","status-publish","format-standard","hentry","category-sharepoint-2010"],"yoast_head":"\n