9.24.42

LTS

March 20, 2026

Mendix Studio Pro is our low-code IDE for professional developers. It's a powerful visual model-driven development environment to build apps on the Mendix Platform. With Studio Pro you can easily create, change, integrate, test and deploy your applications, all in one place. Moreover, you can manage branch lines and security as well as extend your app with custom code using the built-in editors. Click 'Download Studio Pro' to get the installer for free (Windows OS required*). Learn more about the installation and the Studio Pro capabilities in our documentation. Not a professional developer? Learn How Mendix supports different developer profiles .Before installing, please read the Release Notes to learn about improvements, bug fixes, backwards compatibility, breaking changes and known issues. *If you are using a Mac, check out these instructions first.

Release Notes - **Release date: March 20, 2026** ### Improvements - Studio Pro has been updated to run on .NET 10 instead of .NET 8. As a result, .NET 10 is now a required prerequisite for the application. For more information, see [System Requirements](https://docs.mendix.com/refguide9/system-requirements/#software-specifications) - We updated the .NET runtime version installed with Studio Pro to .NET 10.0.3. - We improved the performance of session cleanup. - We changed the level of log messages on the **SystemTask** log node to debug. For non-development deployments this log node was set to info, which was causing too many messages. ### Fixes - We fixed an issue where an import mapping would not read JSON attribute values when a JSON attribute was preceded by another attribute with an attribute name that is a prefix. For example `StatusId` and `Status`. We also improved how JSON objects were read when one object name was a prefix of another object name. (Ticket 266571) - We fixed an issue where changing the queue parallelism through a microflow constant was not working correctly for cluster-wide queues. (Ticket 267097) - We fixed an issue where a long-running after startup microflow causes the node to be assumed crashed by other nodes. (Ticket 269993) - We fixed an issue in import/export mapping in Studio Pro where elements except first of the child array in JSON were omitted.