Connexion v26 modernizes the existing Razor template runtime for .NET 10 and Linux.

The Liquid Template Device included in earlier v26 builds has been removed. Use the FHIR and C-CDA conversion devices, with their custom code hooks, for healthcare format conversion; see FHIR and C-CDA Devices.

Existing Razor-based transformation features now use RazorEngineCore rather than the legacy System.Web-era Razor stack.

The v26 Razor runtime provides:

• .NET 10 and Linux compatibility.

• Removal of the old System.Web dependency chain.

• Cached template compilation.

• A preserved ViewBag and explicit @Raw(...) surface.

• HTML encoding enabled by default.

The encoding default is an intentional safety improvement. Template authors should use @Raw(...) only when the value is known to be appropriate for unescaped output. Existing custom Razor templates should be regression-tested because small surface changes may be required during migration.

1. Identify existing Razor templates and test them on the v26 engine.

2. Review uses of raw, encoded, and attribute output.

3. Check logs and diagnostics without allowing PHI into general operational logs.

4. Load-test large transformations at the intended channel concurrency.

5. Promote templates through the same authorization, audit, and configuration workflow as other channel changes.

• Plugin Developers: What You Need to Know for v26

• FHIR and C-CDA Devices

• Large Message / Attachment Support

• Modern Authentication, Authorization, and Certificates

• Observability, Metrics, and Structured Logging