This is the second post of this series. The previous post can be read at Part 1. The next post can be read at Part 3.
In Part 1, I discussed about:
- Document generation using Content Controls and Open XML 2.0 SDK
- Creating Word templates
- Implementation and samples
In Part 3, I explained one of the ways to “Refresh the document from within the document (e.g., right click on document and click Refresh) using document-level projects for Word 2007 and Word 2010“. In this post, I’ll discuss:
- List of functionalities that can be achieved using the utility/source code
- Description regarding samples provided with utility
- New samples added in this update
The sample document generators are discussed later. The functionalities that can be achieved using the utility/source code are:
Document Generation
- Generate document from a Word template using content controls as place holders and populate controls with data (Object) [
SampleDocumentGenerator
, SampleRefreshableDocumentGenerator
, SampleDocumentWithTableGenerator
] - Generate document from a Word template using content controls as place holders (data bound content controls) and populate controls with data (Object is serialized to XML). [
SampleDocumentGeneratorUsingDatabinding
, SampleDocumentWithTableGeneratorUsingDatabinding
, SampleDocumentGeneratorUsingXmlAndDatabinding
] - Generate document from a Word template using content controls as place holders and populate controls with data (
XmlNode
) [SampleDocumentGeneratorUsingXml
] - Generate document from a Word template using content controls as place holders (data bound content controls) and populate controls with data (
XmlNode
) [SampleDocumentGeneratorUsingXmlAndDatabinding
] - Refresh the document from within the document (e.g., right click on document and click Refresh) using document-level projects for Word 2007 and Word 2010 [Explained in the next post, i.e., Part 3]
- Generate document that can be
- Standalone: Once generated, document cannot be refreshed.
- Refreshable: Once generated, document can be refreshed. Content controls will be added/updated/deleted and content control's content will be refreshed as per data.
- Append documents using
AltChunk
- Protect document
- UnProtect document
- Removal of Content Controls from a document while keeping contents
- Removal of foot notes
- Ensuring that each content control has unique Ids by fixing the duplicate Ids if any for a document
- Serializing an Object to XML using
XmlSerializer
(used for document generation using data bound content controls as serialized object is written to CustomXmlPart
)
Content Controls
- Set text of a content control (not applicable for data bound content controls)
- Get text from a content control (not applicable for data bound content controls)
- Set text of content control while keeping
PermStart
and PermEnd
elements (not applicable for data bound content controls) - Set
Tag
of a content control - Get
Tag
of a content control - Set data binding of a content control
- Set text of a data bound content control from
CustomXmlPart
manually. This is helpful in cases when CustomXmlPart
needs to be removed and this copies the text from the CustomXmlPart
node using XPath.
CustomXmlPart
- Adding a
CustomXmlPart
to a document - Removing
CustomXmlPart
from a document - Getting
CustomXmlPart
from a document - Add/Update an XML element node inside
CustomXmlPart
. This is required
- To keep Document related metadata, e.g., Document type, version, etc.
- To make the Document self-refreshable. In this case, the container content control is persisted inside a Placeholder node, the first time document is generated from template. Onwards when refreshing document, we fetch the container content control from
CustomXmlPart
. - Saving the XML, e.g., serialized object which will be the data store for data bound content controls
Sample Generators
SampleDocumentGenerator
: This sample shows how to generate a non-refreshable document from a template. The content controls are populated using C# code, i.e., not using data bound content controls. The screenshot is: SampleRefreshableDocumentGenerator
: This sample shows how to generate a refreshable document from a template. The content controls are populated using C# code, i.e., not using data bound content controls. This is similar to SampleDocumentGenerator
in implementation. The only difference is the generated document can be refreshed in this case. The screenshot is shown here: SampleDocumentWithTableGenerator
: This sample shows how to generate a refreshable document from a template having Table
. The content controls are populated using C# code, i.e., not using data bound controls. This is similar to SampleRefreshableDocumentGenerator
in implementation. The only difference is that the template has an additional table. The screenshot is shown here: SampleDocumentGeneratorUsingDatabinding
: This sample shows how to generate a refreshable document from a template using data bound content controls. This requires that each of the placeholders (template’s content control) has a predefined XPath. The generated document is similar to SampleRefreshableDocumentGenerator
. SampleDocumentWithTableGeneratorUsingDatabinding
: This sample shows how to generate a refreshable document from a template having table using data bound content controls. This requires that each of the placeholders (template’s content control) has a predefined XPath. The generated document is similar to SampleDocumentWithTableGenerator
. SampleDocumentGeneratorUsingXml
(New): This sample shows how to generate a document from a template using XmlNode
as data. This approach shows that a generic generator can be created which requires XML as data. This requires that XPath for Tag as well as content need to be provided. The content controls are populated using C# code, i.e., not using data bound controls. It covers both direct assignment as well as recursive controls. The generated document is similar to SampleDocumentGenerator
. SampleDocumentGeneratorUsingXmlAndDatabinding
(New): This sample shows how to generate a document from a template using XmlNode
as data and data bound content controls. This approach shows that a generic generator can be created which requires XML as data. This requires that XPath for Tag as well as content needs to be provided. It covers both direct assignment as well as recursive controls. The generated document is similar to SampleDocumentGenerator
.