Connexion v17
This is a placeholder for version 17, expected to come in 2026. Version 17 will likely be the last to run on .NET framework, as we transition to a modern version of .NET.
Version 17 will be an evolutionary branch of version 16.2, which brings Postgres support in addition to the existing Sql Server support. The goal of version 17 is to offer a more cost-effective licensing option for the back end, especially for large organizations which are leveraging cloud options like RDS.
Postgres brings some interesting features to Connexion - specifically its advanced partitioning model. Partitioning lets each queue be backed by a discrete file, but still operates as though there is a single set of master tables. This mostly solves the issue of slow deletes (during maintenance) in Sql Server. Maintenance routines for large deployments should be significantly faster and have lower impact on overall system performance.
Interested in trying out a beta version of v17? Get in touch and we’ll get you an evaluation release.
Version 17 will introduce some breaking changes, including the following:
Move from
System.Data.SqlClienttoMicrosoft.Data.SqlClient. In most cases this will be a transparent change. If you have devices directly referencingSystem.Data.SqlClient, they should be upgraded to referenceMicrosoft.Data.SqlClient. If you are referencing SQL functionality withinConnexion.Core, you will need to recompile your device(s) againstConnexion.Corefrom v17.v17 UIs will be incompatible with v16 services (and visa-versa). The correct version of the associated client application will be automatically launched when selecting an incompatible service (if installed).