The .xsf Manifest File

 <  Day Day Up  >  

The .xsf Manifest File

The manifest file contains many pieces of information that inform the InfoPath client where files relevant to the functioning of the form template are located.

Even a very simple form template has a fairly lengthy manifest.xsf file, as you can see in Listing 15.2. Again, I have edited the file so it displays for printing. (The default extracted file typically contains long lines that require you to scroll horizontally when editing.)

Listing 15.2. The manifest.xsf File Extracted from SimpleControls.xsn
 <?xml version="1.0" encoding="UTF-8"?> <!-- This file is automatically created and modified by Microsoft Office InfoPath. Changes made to the file outside of InfoPath might be lost if the form template is modified in InfoPath. --> <xsf:xDocumentClass  solutionVersion="1.0.0.2"  productVersion="11.0.5531"  solutionFormatVersion="1.0.0.0"  xmlns:xsf="http://schemas.microsoft.com/office/infopath/2003/solutionDefinition"  xmlns:msxsl="urn:schemas-microsoft-com:xslt"  xmlns:xd="http://schemas.microsoft.com/office/infopath/2003"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xmlns:my="http://schemas.microsoft.com/office/infopath/2003/myXSD/2003-12-13T15:12:34">  <xsf:package>  <xsf:files>   <xsf:file name="myschema.xsd">   <xsf:fileProperties>    <xsf:property     name="namespace" type="string"     value="http://schemas.microsoft.com/office/infopath/2003/myXSD/2003-12-13T15:12:34">    </xsf:property>    <xsf:property    name="editability" type="string"    value="full">    </xsf:property>    <xsf:property     name="rootElement" type="string" value="myFields">    </xsf:property>   </xsf:fileProperties>   </xsf:file>   <xsf:file name="template.xml"></xsf:file>   <xsf:file name="sampledata.xml">   <xsf:fileProperties>    <xsf:property name="fileType" type="string" value="sampleData">    </xsf:property>   </xsf:fileProperties>   </xsf:file>   <xsf:file name="view1.xsl">   <xsf:fileProperties>    <xsf:property    name="lang" type="string" value="2057">    </xsf:property>    <xsf:property name="viewWidth" type="string" value="542px">    </xsf:property>    <xsf:property    name="componentId" type="string" value="3">    </xsf:property>   </xsf:fileProperties>   </xsf:file>   <xsf:file name="script.js">   <xsf:fileProperties>    <xsf:property name="scriptType" type="string" value="userEvents">    </xsf:property>   </xsf:fileProperties>   </xsf:file>  </xsf:files>  </xsf:package>  <xsf:importParameters enabled="yes">  </xsf:importParameters>  <xsf:documentVersionUpgrade>  <xsf:useTransform transform="" minVersionToUpgrade="0.0.0.0"></xsf:useTransform>  </xsf:documentVersionUpgrade>  <xsf:views default="View 1">  <xsf:view name="View 1" caption="View 1">   <xsf:unboundControls>   <xsf:button name="CTRL3_5"></xsf:button>   </xsf:unboundControls>   <xsf:mainpane transform="view1.xsl"></xsf:mainpane>  </xsf:view>  </xsf:views>  <xsf:applicationParameters application="InfoPath Design Mode">  <xsf:solutionProperties scriptLanguage="jscript" lastOpenView="view1.xsl"fullyEditableNamespace="http://schemas.microsoft.com/office/infopath/2003/myXSD/2003-12-13T15:12:34"> </xsf:solutionProperties>  </xsf:applicationParameters>  <xsf:documentSchemas>  <xsf:documentSchema rootSchema="yes"location="http://schemas.microsoft.com/office/infopath/2003/myXSD/2003-12-13T15:12:34 myschema.xsd">  </xsf:documentSchema>  </xsf:documentSchemas>  <xsf:fileNew>  <xsf:initialXmlDocument  caption="SimpleControls" href="template.xml">  </xsf:initialXmlDocument>  </xsf:fileNew>  <xsf:scripts language="jscript">  <xsf:script src="script.js">  </xsf:script>  </xsf:scripts> </xsf:xDocumentClass> 

The document element is the xsf:xDocumentClass element, which has multiple attributes that characterize the form template.

The xsf:package element contains information about the files that make up the form template. If you look at each of the xsf:file elements, you will see the name of each form file in the value of the relevant name attribute of an xsf:file element.

The xsf:views element specifies the default view and contains one or more xsf:view elements. Each xsf:view element corresponds to a view that is available when you are designing or using the form template.

The xsf:initialXmlDocument element specifies the XML file that the InfoPath client opens by default. The value of the caption attribute is displayed in the title bar of the InfoPath client.

We will look at the structure of the manifest in more detail in Chapter 16, "The Manifest File."

 <  Day Day Up  >  


Microsoft Office InfoPath 2003 Kick Start
Microsoft Office InfoPath 2003 Kick Start
ISBN: 067232623X
EAN: 2147483647
Year: 2004
Pages: 206

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net