v5.12.3

What's Changed

• Update SmartFormat package to v3.5.0 in #47
• Read the SmartFormat Release Notes for details

Full Changelog: v5.12.2...v5.12.3

v5.12.2

What's Changed

Enhancement: Improve HTML processing for SmartFormat placeholders that are using formatting arguments in #46
Thanks to gferrari-t1 for the support.

Full Changelog: v5.12.1...v5.12.2

v5.12.1

What's Changed

• Update MimeKit package because of a security issue in #43
• Update other package references to latest
• Drop NetCore3.1 in unit tests
• Bump version to v5.12.1 in #44

Full Changelog: v5.12.0...v5.12.1

v5.12.0

What's Changed

• Fix: Update nuget api key in #41
• Fix: Update package references to latest in #42 (Security vulnerabilities of BouncyCastle version < 2.3.1)

Full Changelog: v5.11.1...v5.12.0

v5.11.1

Migrate SmartFormat.NET v2.7.3 to v3.2.1

Heads up

This version is API and source compatible with prior 5.x versions.

In v5.11 the referenced package for SmartFormat.NET is updated from v2.7.3 to v3.2.1. This new major version of SmartFormat.NET incurs breaking changes. MailMergeLib manages breaking API changes under the hood. Other breaking changes are related to using SmartFormat formatter extensions in placeholders:

1. If you're only using plain placeholders like "{Email}" or even "{Today:yyyy-MM-dd}" there's no need for updating the format strings, and you're fine.
2. If you're using formatters like "{Fruit:cond:Apple|Pie|Orange|Banana|No fruit}", where the rendered string depends on the Fruit variable, urgently have a look at https://github.com/axuno/SmartFormat/wiki/Migration#2-formatter-differences-from-v2-to-v3 .Required modifications are not extensive, but unavoidable.
3. On the other side SmartFormat v3 has many advantages:
   • Parsing is 10% faster with 50-80% less GC and memory allocation
   • Formatting is up to 40% faster with 50% less GC and memory allocation
   • Nullable notation inside placeholders
   • much more

See more details here: https://github.com/axuno/SmartFormat/wiki/Why-Migrate

Details

• Update of SmartFormat.NET to v3.2.1 with at least the same extensions enabled as in prior MailMergeLib 5.x versions
• Add NET 6.0 as a target framework, reducing the number of dependencies
• After installation is completed, the above "Heads up" message is displayed
• Add Sandcastle Help File Builder project folder
• Resolves #23

Full Changelog: v5.10.0...v5.11.1

v5.11.0

Migrate SmartFormat.NET v2.7.3 to v3.2.1

Full Changelog: v5.10.0...v5.11.0

v5.10.0

What's Changed

• Update referenced packages in #37
• Resolves: Timing based private key exposure in Bouncy Castle

Full Changelog: v5.9.1.0...v5.10.0

v5.9.1.0

What's Changed

This is a maintenance release

• Change to file-scoped namespaces in solution #29

Update dependencies #34:

MailMergLib:

• Minimum .Net Framework version is 4.6.2
• Update package references
  • AngleSharp 1.0.0
  • MailKit 3.4.3
  • MimeKit 3.4.3
  • YAXLib 4.0.0
  • SmartFormat.NET >= 2.7.3 && < 3.0
• Disable warnings CA5350, CA5351, CA5401

MailMergLib.Tests:

• Update package references
• Remove obsolete SmartObject unit tests

Full Changelog: v5.8.2.0...v5.9.1.0

v5.8.2.0

Updated version of package references:
Set highest major version of compatible dependencies for MailKit, MimeKit, SmartFormat.NET, YAXLib

v5.8.1.0

Fixes

• Fixed: Large embedded images could throw UriFormatException
• Package references: Set version range of compatible dependencies for MailKit, MimeKit, SmartFormat.NET, YAXLib