8. Metadata is read and validated X++ source code is converted to p-code and saved Error logs are created Phase 1 Types and signatures compilation Phase 2 Bodies compilation and p-code generation Phase 3 Phase 2 is re-executed, but only for elements with errors

9. How the Microsoft Dynamics AX compiler works Compilation happens on the client. Metadata is exchanged from SQL all the way to the client and back to SQL Compiler is single threaded

10. Compilation happens on the AOS (no metadata exchange) X++ execution during compilation has been reduced (output log) 64 bit process Single threaded compilation ~30% performance boost

12. AXBuild.exe is a new stand-alone command line tool, to coordinate multiple AOS in the same box to complete a full compilation in parallel Parallelizatio n

14. Private AOS Topology with TFS A private AOS topology is a setup where each developer has his or her own Microsoft Dynamics AX client, AOS instance, model database, and business database. Artifacts are synchronized between developers using a supported version control system like TFS

22. Official documentation for the tool http://msdn.microsoft.com/library/d6da631b-6a9d-42c0-9ffe-26c5bfb488e3.aspx Blog post that explains the architecture of the tool http://blogs.msdn.com/b/axtools/archive/2013/11/04/parallel-x-compilation-for-microsoft-dynamics- ax2012-r2-in-cumulative-update-7.aspx