GroupDocs.Assembly for .NET 26.11 Release Notes
GroupDocs.Assembly for .NET 26.11 lets you validate templates against a JSON Schema, puts loading of external resources under your control, adds document preview generation, and removes empty paragraphs in spreadsheet and plain text templates. <<image>> tags resolve relative paths against the template folder, color tags accept hex strings, and date-only values no longer depend on the server time zone. Templates written for typed objects now work on the same data loaded from JSON, XML or CSV, including $id/$ref references and grouping by nested objects. The release adds a .NET Framework 4.8 build, refreshes the document processing engines, and fixes licensing from a stream, metered licensing, the encoding of text reports, barcodes with a missing font and an extra empty paragraph after HTML content.
Full list of changes in this release
Features
JSON Schema support for JsonDataSource
ASSEMBLYNET-145. A template is checked against the structure of its data before any <<if>> is evaluated. With JSON, that structure was taken from the data itself, so a reference inside a branch that never renders failed when the data behind it was null, an empty array or missing:
<<if [customer.cards.Count() > 0]>>Payment method: <<[customer.cards.First().type]>><</if>>
With "cards": [] or "cards": null, assembly threw “Can not get the value of member ’type’” even though the condition is false.
JsonDataSource now accepts a JSON Schema, the same way XmlDataSource accepts an XML Schema. The template is checked against the schema rather than the data:
- members declared in the schema can be referenced even if they are
null, empty or absent in the data; - members not declared in the schema still fail, so misspelled names are detected as before;
- value types come from the schema, so a
booleanis a Boolean and astringholding digits stays a string.
The customer below has no payment cards and no loyalty data, and its account number is a string of digits:
{ "Name": "Quayside Bistro", "Account": "00042", "Cards": [], "Loyalty": null }
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"Name": { "type": "string" },
"Account": { "type": "string" },
"Cards": {
"type": "array",
"items": { "type": "object", "properties": { "Type": { "type": "string" }, "Last4": { "type": "string" } } }
},
"Loyalty": { "type": ["object", "null"], "properties": { "Level": { "type": "string" } } }
}
}
Template:
Customer: <<[customer.Name]>>
Account number: <<[customer.Account]>>
<<if [customer.Cards.Count() > 0]>>Payment card: <<[customer.Cards.First().Type]>> ending in <<[customer.Cards.First().Last4]>><<else>>No payment card on file.<</if>>
Loyalty program: <<[customer.Loyalty?.Level]>>
using GroupDocs.Assembly;
using GroupDocs.Assembly.Data;
JsonDataSource dataSource = new JsonDataSource("Customer.json", "Customer.schema.json");
DocumentAssembler assembler = new DocumentAssembler();
assembler.AssembleDocument("Json schema.docx", "output.docx", new DataSourceInfo(dataSource, "customer"));
Result:
Customer: Quayside Bistro
Account number: 00042
No payment card on file.
Loyalty program:
Without the schema, the same template fails on customer.Cards.First().Type, and the account number is read as the number 42. Example: AssembleFromJsonWithSchema.cs.
Supported JSON Schema keywords: type (including nullable types such as ["string", "null"]), properties, items, format (date-time and date give date values), enum, const, allOf, and local $ref pointers (#/$defs/..., #/definitions/...). oneOf, anyOf, not, remote or recursive $ref, tuple-form items and arrays of arrays are not supported and cause an exception. With a schema, JsonDataLoadOptions.SimpleValueParseMode and ExactDateTimeParseFormats are not applied (date values must follow ISO 8601), and data members not declared in the schema are ignored.
Boolean values usable directly as conditions. A Boolean member of JSON or XML data (and of any DataTable) is exposed as a nullable Boolean, because the value may be missing. Such a member could not be used directly as a condition and failed with “A conditional expression should return a Boolean value”; item.Enabled == true was required. <<if [item.Enabled]>> now works, with or without a schema; a missing value counts as false.
Document preview with PreviewOptions.Resolution
ASSEMBLYNET-8. DocumentAssembler.GeneratePreview renders pages of a document to images: a template, a document assembled by GroupDocs.Assembly, or any other document of a supported format (word processing, spreadsheet, presentation, email, text). PreviewOptions follows the options of other GroupDocs products, including Resolution.
The example assembles a report into memory and renders its pages to PNG files:
DocumentAssembler assembler = new DocumentAssembler();
using (FileStream template = File.OpenRead("Customer orders.docx"))
using (MemoryStream report = new MemoryStream())
{
assembler.AssembleDocument(template, report,
new DataSourceInfo(new JsonDataSource("Customers.json"), "customers"));
report.Position = 0;
// A stream is created for every page and released when the page is written.
PreviewOptions options = new PreviewOptions(
pageNumber => File.Create($"page{pageNumber}.png"),
(pageNumber, pageStream) => pageStream.Dispose());
options.PreviewFormat = PreviewFormats.PNG;
options.Resolution = 120; // dots per inch; 96 by default
// options.PageNumbers = new[] { 1, 2 }; // all pages by default
assembler.GeneratePreview(report, options);
}
When both Width and Height are set, pages are scaled to fit that size keeping their aspect ratio, and Resolution is ignored. Previews are generated without loading any external resources. Example: GenerateDocumentPreview.cs.
RemoveEmptyParagraphs for spreadsheet and plain text templates
ASSEMBLYNET-36, ASSEMBLYNET-37. DocumentAssemblyOptions.RemoveEmptyParagraphs now works for spreadsheet templates and plain text documents as well. There, a paragraph is a line of text: a line of a cell’s text, or of a text document, that becomes empty after template tags are removed or replaced with empty values is removed together with its line break. Tags such as <<if>> and <<foreach>> written on their own lines no longer leave empty lines behind.
DocumentAssembler assembler = new DocumentAssembler();
assembler.Options = DocumentAssemblyOptions.RemoveEmptyParagraphs;
assembler.AssembleDocument("Empty paragraph.txt", "result.txt", new DataSourceInfo("dummy", "dummy"));
Template:
Prefix
<<[""]>>
Suffix
Prefix
<<if [false]>>
Text to be removed
<</if>>
Suffix
Result:
Prefix
Suffix
Prefix
Suffix
The same template text in a cell of a spreadsheet gives the same result within the cell. Example: RemoveEmptyParagraphs.cs, which assembles the DOCX, PPTX, MSG, XLSX and TXT variants.
Security
Control of external resources referenced by templates and data
ASSEMBLYNET-140. An <<image>> or <<doc>> tag can evaluate to a URI taken from the data, and GroupDocs.Assembly fetched it with no way to prevent it. A server assembling documents from data supplied by others could thus be made to request internal addresses. Template documents can reference network resources too: an image of an HTML template, a linked image or an INCLUDEPICTURE field of a Word document, an external link of a workbook.
GroupDocs.Assembly now tells where each reference to an external resource comes from (ExternalResourceOrigin):
- Template: the template document references the resource itself, including a literal URI of a tag such as
<<image ["https://example.com/logo.png"]>>; - Data: the reference comes from data, such as a URI a tag expression evaluates to, or a resource of a document inserted by
<<doc>>from data.
By default, resources referenced by the template are loaded as before, and resources whose references come from data are skipped. Four LoadSaveOptions properties control this:
SkipExternalResources, true by default: external resources are not loaded;TrustTemplateResources, true by default: resources referenced by the template are loaded even when skipping is on; set it to false when templates come from untrusted sources;WhitelistedResources: host names (a host and its subdomains) or absolute URI prefixes allowed even when skipping is on;ExternalResourceHandler: called for every external resource before it is requested, with itsUri,Originand pre-setSkippeddecision, to allow it, skip it, or provide its content.
In the example, the template inserts an image with <<image [expression]>>, and the image URI comes from data:
const string photoUri = "https://images.example.com/photos/no-photo.jpg";
DocumentAssembler assembler = new DocumentAssembler();
// Default options: the URI comes from data, so the image is skipped and left empty.
assembler.AssembleDocument("Inserting image.docx", "Skipped.docx", new DataSourceInfo(photoUri, "expression"));
// Allow a trusted host and see every decision. The handler can also provide the content itself.
LoadSaveOptions options = new LoadSaveOptions();
options.WhitelistedResources.Add("images.example.com");
options.ExternalResourceHandler = new LocalImageHandler("no-photo.jpg");
assembler.AssembleDocument("Inserting image.docx", "Provided.docx", options, new DataSourceInfo(photoUri, "expression"));
public class LocalImageHandler : ExternalResourceHandler
{
private readonly string mImagePath;
public LocalImageHandler(string imagePath) { mImagePath = imagePath; }
public override void OnLoading(ExternalResourceLoadingArgs args)
{
Console.WriteLine($"{args.Origin} resource {args.Uri}: {(args.Skipped ? "skipped" : "allowed")}");
// Provide the content instead of requesting it.
if (!args.Skipped && args.Uri.StartsWith("https://images.example.com/", StringComparison.OrdinalIgnoreCase))
args.Data = File.ReadAllBytes(mImagePath);
}
}
Output:
Data resource https://images.example.com/photos/no-photo.jpg: allowed
Example: ControlExternalResources.cs.
External resources are resources reaching the network: http, https and ftp URIs, UNC paths (\\host\share) and file URIs with a remote host. Local file paths are not affected, so templates and <<image>> tags using local files keep working. A skipped image of a document is replaced with a transparent image; a skipped <<image>> or <<doc>> value is treated as an empty value.
System.Security.Cryptography.Pkcs updated to patched versions
ASSEMBLYNET-144. The packages now depend on System.Security.Cryptography.Pkcs 8.0.2 (netstandard2.0, net6.0, net8.0) and 9.0.21 (net10.0), which fix CVE-2026-84008 and CVE-2026-70162. dotnet list package --vulnerable no longer reports GroupDocs.Assembly.
Fixes
License.SetLicense(Stream) failed with “Root element is missing”
ASSEMBLYNET-142. A license loaded from a stream was read from the current position of the stream. A stream that has just been written, such as a MemoryStream filled by CopyTo, is positioned at its end, so GroupDocs.Assembly read nothing and threw System.Xml.XmlException: Root element is missing, while other GroupDocs products accepted the same stream. A seekable license stream is now read from its beginning.
using (Stream source = File.OpenRead("GroupDocs.Assembly.lic"))
using (MemoryStream license = new MemoryStream())
{
source.CopyTo(license); // the stream is now positioned at its end
new License().SetLicense(license); // works without license.Position = 0
}
Metered licensing: SetMeteredKey failed with “Authentication failed”
ASSEMBLYNET-143. Metered.SetMeteredKey rejected valid GroupDocs metered keys with InvalidOperationException: Authentication failed, so a customer with a metered license ran in evaluation mode. GroupDocs.Assembly now uses the metered licensing client shared with other GroupDocs products. Consumption is also reported when an operation completes, rather than later from a background thread.
Metered metered = new Metered();
metered.SetMeteredKey("<public key>", "<private key>");
Text and HTML reports lost non-Latin data of ASCII-only templates
ASSEMBLYNET-158. A text or HTML template made of ASCII characters only, with no byte order mark, gave a report in the ANSI code page, on Windows and on Linux: Café was written as 43-61-66-E9 and Привет as ??????. Such a template now gives a UTF-8 report without a byte order mark. A template with a byte order mark, with non-ASCII characters, or with an encoding declared by <meta charset> or an XML declaration keeps its encoding as before.
GroupBy and Distinct over nested objects, $id/$ref in JSON data
ASSEMBLYNET-157. GroupBy(o => o.Customer) and Select(o => o.Customer).Distinct() over a nested object gave one group per row, because every access to a related object looked like a new value. Now:
- in JSON and XML data, nested objects are compared by value, including their own nested objects:
{"Name":"A"}and{"Name":"A"}make one group; - in a
DataSetof your own, rows are compared by identity: orders of the same customer row make one group, two customer rows with equal values stay two groups; - objects of your own classes are compared as .NET does it, nothing changes for them.
JSON written by Json.NET with preserved references failed with NullReferenceException, because an object holding only $ref was lost on loading:
{ "Orders": [ { "Customer": { "$id": "1", "Name": "A" } }, { "Customer": { "$ref": "1" } } ] }
For example, orders 1 and 3 below hold equal customer objects:
{ "Orders": [
{ "Number": 1, "Paid": true, "Customer": { "Name": "Quayside Bistro" } },
{ "Number": 2, "Paid": false, "Customer": { "Name": "Harbor Lane Provisions" } },
{ "Number": 3, "Paid": null, "Customer": { "Name": "Quayside Bistro" } } ] }
This text template:
<<foreach [g in ds.Orders.GroupBy(o => o.Customer)]>><<[g.Key.Name]>>: <<[g.Count()]>> order(s), paid: <<[g.Count(o => o.Paid)]>>
<<foreach [o in g]>> #<<[o.Number]>> <<[o.Paid ? "paid" : "due"]>>
<</foreach>><</foreach>>
JsonDataLoadOptions options = new JsonDataLoadOptions();
options.AlwaysGenerateRootObject = true;
new DocumentAssembler().AssembleDocument("orders.txt", "report.txt",
new DataSourceInfo(new JsonDataSource("orders.json", options), "ds"));
now gives one group per customer:
Quayside Bistro: 2 order(s), paid: 1
#1 paid
#3 due
Harbor Lane Provisions: 1 order(s), paid: 0
#2 due
$ref now gives a copy of the object it names, so <<[o.Customer.Name]>>, OrderBy and GroupBy work. Objects with different $id values are different objects even if their values are equal. An object may refer to an object holding it (Order.Customer to the customer of the order): its simple values are available, and its member that would repeat the path (Order.Customer.Order) gives the parent object. A $ref without a matching $id is ignored. Data that would grow over one million nodes because of references fails with a clear error.
Barcode failed when the font of its text box is not installed
ASSEMBLYNET-160. A QR code, and other barcode types whose code text is drawn by the engine (DataMatrix, Aztec and others), failed with Value cannot be null. (Parameter 'trueTypeFont') if the font of the text box holding the tag was not installed, typically Calibri on Linux. The code text now uses a fallback font. If the system has no fonts at all, the barcode is generated without its text.
MSG report kept the template’s conversation topic
ASSEMBLYNET-159. Tags in the subject of an MSG template were replaced in PR_SUBJECT and PR_NORMALIZED_SUBJECT, but PR_CONVERSATION_TOPIC kept the tag, for example <<[subject]>>. Outlook threads messages by this property, and some clients show it. Tags in the conversation topic are now processed as well.
Clear error for a doc tag in spreadsheet, presentation and text templates, no empty file after a failure
ASSEMBLYNET-152. A <<doc>> tag in a template of these formats failed with “Tag ‘doc’ is not well-formed. Token ‘doc’ is unexpected.”, which pointed to the syntax of the tag. The error now says that the tag is not supported for the template format:
Tag 'doc' is not supported for this template format. Documents can be inserted into Word Processing templates and email templates with HTML or RTF bodies only.
DocumentAssembler.AssembleDocument with an output path also left an empty file there when it failed with an exception. The file is now removed.
Extra empty paragraph after HTML content at the end of a paragraph
ASSEMBLYNET-182. An -html expression tag ending its paragraph left an empty paragraph after HTML ending with a block element, such as <p>A</p><p>B</p>. The template paragraph now ends with the last HTML paragraph:
| Template paragraph | Before | Now |
|---|---|---|
<<[html] -html>> | A, B, empty paragraph | A, B |
Text: <<[html] -html>> | Text:, A, B, empty paragraph | Text:, A, B |
Text: <<[html] -html>>End | Text:, A, B, End | unchanged |
HTML ending with a table keeps the paragraph after the table.
Enhancements
Dates, numbers and Booleans of JSON, XML and CSV data work in templates like those of typed objects
ASSEMBLYNET-155. Values of file data sources may be missing, so they reach a template as Nullable<T>. A template written for typed objects failed on the same data loaded from a file, and needed o.Date.Value.Month and o.Paid == true. Now these expressions work with JSON, XML and CSV data, and with Nullable<T> members of your own classes:
<<[o.Date.Month]>> <<[o.Date.AddDays(1):"dd.MM.yyyy"]>> <<[o.Total.ToString("F2")]>>
<<[o.Paid ? "paid" : "due"]>> <<if [o.Paid && o.Date.Year == 2026]>>...<</if>>
<<foreach [o in orders.Where(x => x.Paid)]>>...<</foreach>> <<[orders.Count(x => x.Paid)]>>
For a missing value, a member gives an empty value and a condition is false. Value, HasValue and the other members of Nullable<T> keep their meaning, so existing templates give the same result.
In the example, every order of Customers.json refers to its customer with "$ref" (JSON written by Json.NET with preserved references), and the template uses order dates as plain dates:
<<foreach [c in customers]>>Customer: <<[c.CustomerName.Trim()]>>
<<foreach [o in c.Order.OrderBy(x => x.OrderDate)]>><<[o.OrderDate.Month]>>/<<[o.OrderDate.Year]>>: <<[o.Product.ProductName]>> for <<[o.Customer.CustomerName.Trim()]>>, <<[o.Customer.ShippingAddress]>>
<</foreach>><</foreach>>
new DocumentAssembler().AssembleDocument("Customer orders.docx", "output.docx",
new DataSourceInfo(new JsonDataSource("Customers.json"), "customers"));
Result (excerpt):
Customer: Ali Ahmed
2/2015: Lenovo G50 for Ali Ahmed, Quette House, Park Road, ISB
6/2015: Nexus 5 for Ali Ahmed, Quette House, Park Road, ISB
10/2015: Pavilion G6 for Ali Ahmed, Quette House, Park Road, ISB
Example: UseFileDataLikeTypedObjects.cs, which also shows GroupBy over a nested object (ASSEMBLYNET-157).
Images in table cells and group shapes of presentations
ASSEMBLYNET-52. In a presentation template, an <<image>> tag could only be placed in a textbox. Placed in a table cell, it failed with “Tag ‘image’ must be located within an image container”, so a table listing items with their pictures could not be built. Tags of any kind in shapes of a group shape were not processed and remained in the output.
A table cell is now an image container: the image becomes the picture fill of the cell, including cells of rows repeated by <<foreach>>:
| Name | Photo |
|---|---|
<<foreach [p in products]>><<[p.Name]>> | <<image [p.Photo] -fitHeight>><</foreach>> |
Product[] products =
{
new Product { Name = "Logo", Photo = "Images/Logo.jpg" },
new Product { Name = "No photo", Photo = "Images/no-photo.jpg" },
};
new DocumentAssembler().AssembleDocument("Image in table cell.pptx", "output.pptx",
new DataSourceInfo(products, "products"));
public class Product
{
public string Name { get; set; }
public string Photo { get; set; }
}
With -fitHeight, the row grows to show the image with its aspect ratio. The other fit switches keep the aspect ratio of the image within the cell, because the width of a cell is the width of its whole column. Shapes of group shapes, including nested groups, are processed like other shapes. Example: InsertImageIntoTableCell.cs.
Relative image paths are resolved against the template folder
ASSEMBLYNET-62. An <<image>> tag that gets a relative file path from data, such as "Images/photo.png", failed with “Cannot load an image using the provided string value” unless the path was relative to the current directory of the application. A relative path is now resolved against the folder of the template first, by analogy with linked resources of Microsoft Office documents. For a template loaded from a stream, set the folder with LoadSaveOptions.ResourceLoadBaseUri. If no file exists there, the current directory is used as before.
Templates are in C:\Reports\Templates and images in C:\Reports\Images, and the template inserts <<image [expression]>>:
const string relativePath = "../Images/no-photo.jpg";
DocumentAssembler assembler = new DocumentAssembler();
// A template loaded from a file: the path is resolved against the folder of the template.
assembler.AssembleDocument(@"C:\Reports\Templates\Inserting image.docx", "output.docx",
new DataSourceInfo(relativePath, "expression"));
// A template loaded from a stream has no folder: set it with ResourceLoadBaseUri.
LoadSaveOptions options = new LoadSaveOptions();
options.ResourceLoadBaseUri = @"C:\Reports\Templates";
using (FileStream template = File.OpenRead(@"C:\Reports\Templates\Inserting image.docx"))
using (FileStream report = File.Create("output-from-stream.docx"))
{
assembler.AssembleDocument(template, report, options, new DataSourceInfo(relativePath, "expression"));
}
Example: InsertImageFromRelativePath.cs.
Hex color strings in backColor and chart color tags
ASSEMBLYNET-25. A color given as a string now can be a hex value: "#RRGGBB", "#RGB" or "#AARRGGBB", in addition to a color name ("red") and an ARGB integer. For example, <<backColor [item.Color]>> with "#FF0000" coming from data now applies red. Before, hex strings gave no color.
<<foreach [s in statuses]>><<backColor [s.Color]>><<[s.Name]>><</backColor>>
<</foreach>>
OrderStatus[] statuses =
{
new OrderStatus { Name = "Paid", Color = "#C6EFCE" },
new OrderStatus { Name = "Pending", Color = "#FFEB9C" },
new OrderStatus { Name = "Overdue", Color = "#F00" },
new OrderStatus { Name = "Cancelled", Color = "LightGray" },
};
new DocumentAssembler().AssembleDocument("Hex color.docx", "output.docx",
new DataSourceInfo(statuses, "statuses"));
The four lines get the backgrounds C6EFCE, FFEB9C, FF0000 and D3D3D3. Example: SetBackColorFromHexString.cs.
Date-only values in JSON and CSV data keep their date regardless of the server time zone
ASSEMBLYNET-151. Since 26.6, a date-only value such as "2020-01-01" loaded by JsonDataSource or CsvDataSource was shifted by the UTC offset of the server: on a UTC+2 server it became 2019-12-31 22:00, so <<[date]:"dd.MM.yyyy">> printed 31.12.2019. Date-only values now keep their date: the same template prints 01.01.2020 on any server. Values with Z or an offset (2024-11-03T23:00:00Z, 2024-11-03T23:00:00+02:00) still keep their exact instant, as introduced in 26.6, and the result does not depend on the server time zone.
.NET Framework 4.8 (net48) build added
ASSEMBLYNET-147.
Starting with this release, GroupDocs.Assembly for .NET includes a build for .NET Framework 4.8 (net48).
Microsoft ends support for .NET Framework 4.6.2 on January 12, 2027. After that date, we will continue shipping the .NET Framework 4.6.2 build (net462) as deprecated for a few more months, and then remove it. From that point, .NET Framework 4.8 will be the minimum supported .NET Framework version.
What this means for you
- Projects targeting .NET Framework 4.8 or 4.8.1 get the new
net48build automatically from NuGet — no code changes required. - Projects targeting .NET Framework 4.6.2–4.7.2 keep working with the
net462build for now. We recommend moving them to .NET Framework 4.8 before January 2027.
Upgrade document generation engines to 26.10
ASSEMBLYNET-148.
| Engine | Version |
|---|---|
| Word-processing engine | 26.10 |
| Spreadsheet engine | 26.10 |
| Presentation engine | 26.10 |
| Email engine | 26.9 |
| Barcode engine | 26.10 |
The packages now depend on SkiaSharp 4.152.1, Aspose.Drawing.Common 26.10.0 and System.Formats.Asn1 9.0.21.
Public API and Backwards Incompatible Changes
New public API
| Type | Member |
|---|---|
JsonDataSource | JsonDataSource(string jsonPath, string jsonSchemaPath) |
JsonDataSource | JsonDataSource(string jsonPath, string jsonSchemaPath, JsonDataLoadOptions options) |
JsonDataSource | JsonDataSource(Stream jsonStream, Stream jsonSchemaStream) |
JsonDataSource | JsonDataSource(Stream jsonStream, Stream jsonSchemaStream, JsonDataLoadOptions options) |
LoadSaveOptions | bool SkipExternalResources { get; set; } (default true) |
LoadSaveOptions | bool TrustTemplateResources { get; set; } (default true) |
LoadSaveOptions | List<string> WhitelistedResources { get; set; } |
LoadSaveOptions | ExternalResourceHandler ExternalResourceHandler { get; set; } |
ExternalResourceHandler | virtual void OnLoading(ExternalResourceLoadingArgs args) |
ExternalResourceLoadingArgs | string Uri { get; }, ExternalResourceOrigin Origin { get; }, bool Skipped { get; set; }, byte[] Data { get; set; } |
ExternalResourceOrigin | Template, Data |
DocumentAssembler | void GeneratePreview(string documentPath, PreviewOptions previewOptions) |
DocumentAssembler | void GeneratePreview(Stream documentStream, PreviewOptions previewOptions) |
PreviewOptions | CreatePageStream, ReleasePageStream, PreviewFormat, PageNumbers, Width, Height, Resolution |
PreviewFormats | PNG, JPEG, BMP |
CreatePageStream, ReleasePageStream | delegates |
Backwards incompatible changes
<<image [item.PhotoUrl]>> where PhotoUrl is an http/https URI. Add the hosts to LoadSaveOptions.WhitelistedResources, or set LoadSaveOptions.SkipExternalResources to false to keep the previous behaviour. Resources referenced by the template itself are loaded as before.- A call such as
new JsonDataSource(path, null)with a literalnullsecond argument is now ambiguous at compile time. Cast the argument:new JsonDataSource(path, (JsonDataLoadOptions)null). Compiled applications are not affected. - Reports of ASCII-only text and HTML templates without a byte order mark are now in UTF-8 instead of the ANSI code page (ASSEMBLYNET-158). Only non-ASCII data is written differently, and an MHTML report saved from such a template declares
charset="utf-8". To keep the ANSI code page, declare it in the template (<meta charset>in HTML) or add a non-ASCII character in that encoding. GroupByandDistinctover nested objects of JSON, XML andDataSetdata now merge equal objects, where they gave one group per row (ASSEMBLYNET-157).- With
DocumentAssemblyOptions.AllowMissingMembers,<<[o.Date.Month]>>over a nullable value now prints the month, where it printed nothing (ASSEMBLYNET-155). - The text of the exception for a
doctag in spreadsheet, presentation and text templates has changed (ASSEMBLYNET-152). The exception type is the same. - An
-htmltag ending its paragraph no longer leaves an empty paragraph after HTML ending with a block element (ASSEMBLYNET-182). To keep a blank line, end the HTML with<p> </p>.
Important Notes for Generated Documents
Because the underlying engines were refreshed, regenerated documents may differ at the byte level while remaining visually and functionally equivalent: engine version stamps, paragraph identifiers of Word documents, PNG encoding of inserted images (pixel-identical), MIME boundaries of email messages. Consumers who byte-compare generated output against stored baselines should refresh those baselines after upgrading.