Microsoft Dynamics 365 and Power Platform Library

Few settings to configure in Microsoft Visual Studio to make the development experience with AX a little smoother. Go to Dynamics 365 Options Set Projects Options - organize project by element type Set Text Editor Options - Line number and word wrap Set Best practice options The definition of best practice rules set is per model, by default it is set to Application Common model and can be switched between different models from the combo box in the upper right corner. Let's say if you are working with Customization Analysis you have to check Microsoft.Dynamics.AX.Framework.CustomizationAnalysisRules best practice rule. Set BP rules at Build level Build process itself does BP checking - there is an option to enable it. To take this into effect you might have to rebuild the solution/project rather build it.

AX 7 is impending with a radical technical and structural change in the world of Microsoft ERP, Dynamics AX, in contrast to what we got in current version AX 2012. This is a soft indication to all developers to get ready to adopt this change nippily. There is a lot to learn on AX 7 development while supporting\working with current versions of Dynamics AX :( Back to file system; Yes, with AX 7 we are back to file system. Any change (technical) we make in application is saved into file (XML file) at your disk. Before we talk about the main artefacts involved in AX 7 development and the approach we will be using while developing in AX 7 world. Let's put some glance on Development environment how will it looks like, what we (developer) will have in our DEV box. Visual Studio will be used for all development stuff;  MS  developed visual studio extensions using standard Visual Studio extensions to enable the development of X++ code and AX 7 metadata in ...

Exam  MB6-890 https://www.microsoft.com/en-us/learning/exam-mb6-890.aspx

http://www.bdosolutions.com/ca/insights/microsoft-convergence-update-part-3-dynamics-ax-roadmap-and-strategy-microsoft-dynamics-ax-7-0/