An InfoPath form template is actually a CAB File containing different component files.

Below is a list of files which forms part of an InfoPath template.

• .xsf file: A manifest file that describes the basic definition of other form files.
• .xsl file: Defines the transformation for data into different views.
• .xsd file: Defines the data source schema.
• .dll file: Carries the custom logic built into .NET or COM.
• .htm and other RESOURCE files: Custom HTML resource files and other RESOURCES for the form.

When a form template is uploaded using Administrative deployment, the template is STORED in the content database of the SITE. Office Forms Services provide a server-runtime environment for InfoPath Forms Services. While running on the browser, all rules, validations, and calculations are executed in the browser using client-side script.

All business logic is executed on the server. So when a browser requests business logic execution, a post back is executed using low cost XMLHTTP. Formserver.aspx is an InfoPath Forms Services page that accesses the form’s data from the content database and renders it to the client.

An InfoPath form template is actually a CAB File containing different component files.

Below is a list of files which forms part of an InfoPath template.

When a form template is uploaded using Administrative deployment, the template is stored in the content database of the site. Office Forms Services provide a server-runtime environment for InfoPath Forms Services. While running on the browser, all rules, validations, and calculations are executed in the browser using client-side script.

All business logic is executed on the server. So when a browser requests business logic execution, a post back is executed using low cost XMLHTTP. Formserver.aspx is an InfoPath Forms Services page that accesses the form’s data from the content database and renders it to the client.