GroupDocs.Assembly for .NET 25.12 Release Notes Leave feedback

The GroupDocs.Assembly for .NET 25.12 release introduces significant enhancements for OOXML compliance handling and fixes critical issues with template expression processing and barcode generation.

OOXML Compliance Support: This release adds comprehensive support for OOXML compliance levels in Word documents. You can now explicitly specify the compliance level (Ecma, Transitional, or Strict) when saving documents, and the system automatically preserves the original document’s compliance when appropriate.

Template Expression Processing: Fixed an issue where template expressions inside inline content controls (SdtRun) were not being processed, ensuring all template expressions are correctly replaced regardless of their location in the document.

Barcode Generation Reliability: Improved barcode generation on Linux platforms by properly handling transparent colors and enforcing minimum dimensions for Codabar barcodes, ensuring barcodes render correctly across all platforms.

Note

This section outlines public API changes introduced in GroupDocs.Assembly for .NET 25.13. It includes new and deprecated methods, as well as internal behavioral changes that may affect existing implementations. Any regression or modified behavior is highlighted here.

A new public enumeration OoxmlCompliance has been added to specify the OOXML compliance level when saving Word documents to OOXML formats:

namespace GroupDocs.Assembly
{
    /// <summary>
    /// Specifies the OOXML compliance level to use when saving Word documents to OOXML formats.
    /// </summary>
    public enum OoxmlCompliance
    {
        /// <summary>
        /// Specifies ECMA-376 compliance level.
        /// </summary>
        Ecma,
        
        /// <summary>
        /// Specifies ISO/IEC 29500:2008 Transitional compliance level.
        /// </summary>
        Transitional,
        
        /// <summary>
        /// Specifies ISO/IEC 29500:2008 Strict compliance level.
        /// </summary>
        Strict
    }
}

Available Options:

• Ecma: Specifies ECMA-376 compliance level
• Transitional: Specifies ISO/IEC 29500:2008 Transitional compliance level (commonly used for compatibility)
• Strict: Specifies ISO/IEC 29500:2008 Strict compliance level (fully compliant with the standard)

A new nullable property OoxmlCompliance has been added to the LoadSaveOptions class:

public class LoadSaveOptions
{
    /// <summary>
    /// Gets or sets the OOXML compliance level to use when saving Word documents to OOXML formats.
    /// The default value is null, which means the compliance level will be determined automatically.
    /// </summary>
    public OoxmlCompliance? OoxmlCompliance { get; set; }
}

Usage:

• When set to null (default): The system automatically preserves the original document’s compliance level if it was Transitional, otherwise uses Strict compliance
• When explicitly set: The specified compliance level will be used when saving to OOXML formats
• This property only applies to OOXML formats (DOCX, DOCM, DOTX, DOTM, FlatOpc, etc.) and is ignored for other file formats

The following code snippet demonstrates how to explicitly specify the OOXML compliance level when assembling a Word document:

var source = "template.docx";
var target = "output.docx";
var data = "data.json";

// Create LoadSaveOptions with explicit OOXML compliance
var options = new LoadSaveOptions(FileFormat.Docx);
options.OoxmlCompliance = OoxmlCompliance.Strict; // or Ecma, Transitional

var dataSourceInfo = new DataSourceInfo(new JsonDataSource(data));
var assembler = new DocumentAssembler();
assembler.AssembleDocument(source, target, options, dataSourceInfo);

When OoxmlCompliance is not explicitly set (default null), the system automatically preserves the original document’s compliance level if it was Transitional:

var source = "template_transitional.docx"; // Document with Transitional compliance
var target = "output.docx";
var data = "data.json";

// OoxmlCompliance is null by default - original compliance will be preserved
var options = new LoadSaveOptions(FileFormat.Docx);
// options.OoxmlCompliance is null - automatic preservation

var dataSourceInfo = new DataSourceInfo(new JsonDataSource(data));
var assembler = new DocumentAssembler();
assembler.AssembleDocument(source, target, options, dataSourceInfo);
// Output document will maintain Transitional compliance

Template expressions inside inline content controls (SdtRun) are now properly processed. The following example demonstrates that expressions work correctly in all content control types:

var source = "template_with_sdtrun.docx";
var target = "output.docx";
var data = "data.json";

// Template document contains:
// - SdtBlock: <<[field1]>>
// - SdtRun (Inline): <<[field2]>>  // Now properly processed
// - Regular text: <<[field3]>>

var options = new LoadSaveOptions(FileFormat.Docx);
var dataSourceInfo = new DataSourceInfo(new JsonDataSource(data));
var assembler = new DocumentAssembler();
assembler.AssembleDocument(source, target, options, dataSourceInfo);
// All template expressions are now correctly replaced, including those in SdtRun