The new X++ compiler and the Microsoft Dynamics AX development platform click to listen
Strange things were afoot at the Tech Convention and the Earl of Villadsen and the Duke of Robear were giving us a heavy dose of "Check this out," during the developer sessions!
The X++ code base is not well-structured for larger data sets and VS projects and therefore the concept of loading everything into one project would be unbearable. Now there is an assembly for each package. These assemblies are composed of net modules and PDB files. each NM contains code for artifacts that are similar in nature. This makes for more efficient use.
AX has introduced IGNORE LIST of for code assemblies that push the boundaries of code generation and legacy code.
Customizations to AX 7 are now stored as DELTAS in the XML file structure to allow for ease of compilation and migration.
This is one area where the group has most triumphantly optimized for SPEED. Robert indicated that 92% of conflict auto resolved in code migration from 2012 to AX 7. This has opened the ease of implementation and migration of ISV solutions. This is how AX 7 was able to ship with 50+ ISV solutions.
"When I cut into software I want to see it bleed XML." - Peter Villadsen.
By exporting error messages in XML a developer can more easily search, organize, and handle the issues.
The compiler is also a multi-pass for error handling like C# and gives the developer a much more robust look at the depth of the error instead of the old X++ surface error returns.
Cross reference has been simplified down to two main tables for use.
Opening these files in the editor will give a path to the AX artifacts.
Using this path a developer can send URL representation of the XML to a person as link that will bring the recipient directly to the issue, ready to work.
Best practices are available and more robust VS, allow for the user to quickly find the area of concern. It is very easy for a user to write custom best practice rules
The debugger that AX was using is gone. Gone, gone. On the side of a milk carton disappeared. Once the the group got the X++ code to generate as IO code, VS is now able to debug in the natural VS environment. The team has made some tweaks to bend the debugger towards AX7... read more here in the AX wiki detailing regarding debuggers.
All of us in San Dimas and beyond can relax and remember to be XLNT to each other... and Party On DUDES!
No comments:
Post a Comment