In this post, we provide high level definitions for some basic concepts for AX7 Development. Not all of these concepts are new, so it will be a piece of cake for all AX developers.
This post will be used as a reference post for the next posts coming in #AX7SERIES
Any AOT element like form or table (similar to AX2012)
Logical grouping of AOT Elements (similar to AX2012)
Grouping of elements representing distributable software solution. One element can only exist in one model, not the other. Design time concept
New concept in AX 7. Deployment unit. Contains one or more models. Can be exported to file which can be deployed on other environments like staging or production
#AX7SERIES: Power of Visual Studio IDE
The #AXSERIES is an attempt to cover all the new things in the development paradigm in AX7 with a difference oriented approach between the ex and new version of the ERP making it easier for the developers to jump in the new environment
AudienceAX 7 enthusiasts, Dynamics AX 2012 (FP, R2 R3) X++ Developers, Functional and Technical consultants and advanced users
Ok I somehow managed my time to continue this blog series. I tell you what, I am not very busy actually, but still I dont know where my time goes :D
Anyways cutting the chatter, lets get straight to the point. This blog post will share some intersting things that were totally IMPOSSIBLE in AX AOT IDE thus titling this "POWER OF Visual Studio IDE"
Categorization of AOT Items
IDE provides two ways or views to see and access AOT ItemsSame old way (new color scheme due to whole new IDE though :P) illustrated as follow
Provides a list of Models stored as default by the installation along with new models created by devs.
Search AOT Items
Second is the searching. Imagine how quick the access would become if you can search in the whole AOT without going to a specific node, what we call in Arabic, "Halwa" #sweat
Saving development items on local machine
Yes sir, in #AX7, you code gets saved in your local folder. You sync with AOS at later stage perhaps.
Code windows and tabs: Beautifullll
Why I am getting so excited is due to the HUGE PLUS we will get after migrating to the VS IDE. Imagine no more scrolls and clicks in the left method list. All code for one class / table in one code window with multiple code sub tabs openable
Enjoy links section as cool as ever
- Link 1
- Link 2
- Link.... n
#AX7SERIES: Welcome To Visual Studio
SubjectThis post is the first on the series of AX7 which will feature introduction and the underlying changes
AudienceVisual Studio developers, Dynamics AX 2012 (FP, R2 R3) X++ Developers, Technical consultants and advanced users
Since you know that AX7 is out for first look and demos, And the good thing for the all time old school devs is, the long awaited VS integration is here. AX 7 development is completly shifted on Visual Studio. Now since all the old school VS Devs (including me of course) are so fond of the VS IDE (which is probably the best IDE there is), think how cool, quick and smart the work would get when its all done in VS.
Secondly, we have some new things to learn as the framework has just been upgraded a little bit. Obviously not a very big change compared to the 2009 - 2012 transition, but not a small one either.
Take this for example, all new development artifacts would be stored on local dev machine in the form of files. Quite contrasting to AX 2012 isn't it.
With VS 2015+ as the version for development, the performance requirements have also plussed. The same is illustrated in the following snapshot taken from one of the official training videos on DLP
|AX7 Development - Visual Studio requirements|
To cater all this, we need a deep study of all such changes and the new things introduced. This is why we have started the new AX7 series which will cater all of this to be shared on this blog. So stay tuned #DAX7ers.
BY THE WAY Enjoy some cool links in the end