XSLT

Converting an InfoPath 2007 Form into a Word 2007 Document

David Gerhardt — Fri, 08 Aug 2008 22:20:11 GMT

With the introduction of the Office Open XML Formats in the 2007 release, the process for programmatically using XSLT to generate Word 2007 documents has changed somewhat since the Office 2003 days. For those of you not interested in working with XSLT, this post describes an alternative for programmatically generating Word 2007 documents from InfoPath 2007 forms...

XSLT 2.0 and XPath 2.0

David Gerhardt — Tue, 23 Jan 2007 17:34:00 GMT

The World Wide Web Consortium (W3C) published a few recommendations today, two of which include XSLT 2.0 and XPath 2.0. The Version 1.0 recommendations for these XML standards were published in November 1999, so updates were long overdue. However, there are products currently available that already use the standards. XSLT processors such as Saxon have been compliant with XSLT 2.0 and XPath 2.0 working drafts and candidate recommendations for several years now. It will be interesting to see how quickly other technologies incorporate the updates...

Good Online XSLT Resource

David Gerhardt — Thu, 16 Feb 2006 18:43:00 GMT

Michael Kay, editor of the W3C XSLT 2.0 candidate recommendation and author of several reference books for XSLT and XPath, recently joined the blogging community. On February 3 Kay launched Saxon Diaries, which focuses on his Saxon processor but also has general information related to XSLT, XPath, and XQuery. Kay's site is a welcome addition to the relatively small number of online XSLT resources.

More on Transforming InfoPath Images into WordML

David Gerhardt — Tue, 08 Nov 2005 20:21:00 GMT

Last month, I wrote about transforming InfoPath form files that contain ink picture controls into Word 2003 documents. That task involved getting the ink picture data and associated background image from the form file into WordML. This month, the task at hand was the transformation of form files with a variable number of images into WordML. This type of transformation is similar to the one regarding the ink picture, except that the number of images to be transformed at runtime is unknown...

Transforming an InfoPath Ink Picture into WordML

David Gerhardt — Fri, 21 Oct 2005 17:46:00 GMT

On a current project I was tasked with using XSLT to transform InfoPath form files into Word 2003 documents. The InfoPath form template used to create the XML input was designed for a tablet PC and thus had an ink picture control, the data for which needed to appear in the corresponding Word document. To complicate matters, the ink picture in the form template used a background image, which also needed to be output in Word...

Transforming InfoPath Rich Text into WordML

David Gerhardt — Fri, 12 Aug 2005 20:41:00 GMT

NOTE: This post is actually a repeat of one that was authored last June. Unfortunately, that post resides on another blog server that is no longer public. So, in response to a recent question about transforming InfoPath rich text into Word, I have decided to re-post. Amazingly, the content is still valid, even though Microsoft has since released its XSLT Inference Tool...

Generating WordML in InfoPath and Opening the Results in Word

David Gerhardt — Fri, 17 Dec 2004 09:24:00 GMT

We were recently tasked with generating WordML output from an InfoPath SP1 form and then loading the output in Word. The XSL stylesheet for our transform had already been developed, and it was too complex for the InfoPath to Word Wizard (which is included in the InfoPath 2003 SDK). As a result, we were left to solve the problem using managed code in our form solution.

John and I separately found the same reference, which demonstrated how an XSL resource file could be used to transform a form's data source. We took that example and went a few steps further, saving the result of the transform to an XmlDocument object, instantiating Word, and inserting the XmlDocument object into a new Word document. Our code looked as follows:

// First create a COM DOM and load the XSL resource file into that DOM.

IXMLDOMDocument domDocument = thisXDocument.CreateDOM();

domDocument.load("EmployeeReview.xsl");



// Create an XmlDocument object and load the XML of the DOM.

XmlDocument xsltDocument = new XmlDocument();

xsltDocument.LoadXml(domDocument.xml);



// Load the InfoPath XML into an XmlDocument object.

XmlDocument infoPathDocument = new XmlDocument();

infoPathDocument.LoadXml(thisXDocument.DOM.xml);



// Load the XSL XmlDocument object into an XslTransform object.

XslTransform xslt = new XslTransform();

xslt.Load(xsltDocument.CreateNavigator(), new XmlUrlResolver(),

  this.GetType().Assembly.Evidence);



// Create an output XmlDocument object and load the results of the transform.

XmlDocument outputDoc = new XmlDocument();

outputDoc.Load(xslt.Transform(infoPathDocument.CreateNavigator(), null, new XmlUrlResolver()));



// Instantiate Word and insert the output XmlDocument object into a new document.

object missing = System.Reflection.Missing.Value;

Word.Application wordApp = new Word.ApplicationClass();

Word.Document oDoc = new Word.DocumentClass();

oDoc = wordApp.Documents.Add(ref missing, ref missing, ref missing, ref missing);

wordApp.Selection.Range.InsertXML(outputDoc.OuterXml,ref missing);

wordApp.Visible = true;

Note that using this code requires references to the Word COM object (Microsoft Word 11.0 Object Library) and the System.Xml.dll .NET component. In addition, the following directives were added to our form code file:

using System.Xml;

using System.Xml.Xsl;

using Word = Microsoft.Office.Interop.Word ;