0

Hi everyone, I'm currently writing my bachelor's thesis on linting tools—specifically comparing traditional code linters with low-code linters like MxLint in Mendix. To create a meaningful comparison, I want to understand how the Mendix build process works under the hood—especially how and when code or logic gets compiled or transformed during the application lifecycle. In traditional development, the build pipeline is usually very transparent. For example: When developing in C++, the IDE creates a .cpp file, which is then compiled into a .exe file that can be executed. In Python, the IDE generates a .py file, which is interpreted and executed directly without a separate compilation step. I’m trying to find out how Mendix fits into this picture: What exactly happens when a Mendix app is built (built process)? Is there a code generation step (e.g. Java or other artifacts)? How are .mpr files created during the development process in Studio Pro (since these files are the starting point for the MxLint linting process)? How do files like .mpr and .mda fit into the overall lifecycle? Are they intermediate representations, final outputs, or something else? I've already watched the "Under the Hood of Studio Pro" videos, but unfortunately, they either didn’t address these specific questions or remained too simple for my needs. I understand that the exact implementation details might be proprietary, but I’m mainly interested in understanding the abstract or conceptual workflow behind how Mendix applications are built. Any technical documentation, high-level architecture diagrams, or insights from your experience would be super helpful. I’m trying to get a clear picture of the Mendix pipeline so I can relate it to how traditional linters (like Pylint) hook into conventional build processes. Thanks so much in advance! Best regards,Sinar

asked 2025-04-15

0 answers