Over the last few years I've talked a lot (both online and offline) about how we should all strive to put software engineering practices back into AX. What I mean by that is that we've become lazy in how we do and manage our development, because AX has certain features that allows us to do just that. But with the product growing bigger, the features becoming more advanced and the projects getting bigger and more complex, the need to go back to those good practices has grown as well. As a result, the demand for Version Control and other development best practices for AX has become bigger. With the release of "the new" Microsoft Dynamics AX, some major shifts in this regard are happening. All for the better, but for some people this may represent a departure of some AX-specific practices.
Starting next week, I will be posting this blog post series "Design - Compile - Run" as a guide into paradigms and their meanings, starting with AX 2012 and leading into the new Microsoft Dynamics AX. I hope this will help serve as a guide to get your AX 2012 development processes in line and ready for the new AX. Discussing some details of designing, compiling and running AX is valuable information and will help you understand the new AX better.
Part 1: AX 2012 Paradigms
Part 2: Design, Compile, Run in AX 2012
Part 3: Design, Compile, Run in the new AX
Part 4: the new AX Paradigms