Efficient Development in Visual Studio
When integrating to Microsoft Dynamics AX you have to use the Microsoft Dynamics AX Business Connector.
The Business Connector does provide access to the Microsoft Dynamics AX Application, but the
surface / interface of the Business Connector does not reflect the interface of
the Microsoft Dynamics AX Application.
This results in the lack of support for the modern productivity enhancing features
of Visual Studio like Intellicense, automatic syntax and compilation verification.
If a change is made to the Microsoft Dynamics AX Application that changes the interface (like renaming a class or table field), there will be no compilation
errors generated in the Visual Studio Solution, because the Business Connector does not provide
the compiler any information about what is correct and valid in regards to the
Microsoft Dynamics AX Application.
With AX.NET this all changes! The AX.NET technology is based upon the AX.NET Assembly
that is automatically generated by the AX.NET Assembly Generator. The AX.NET Assembly contains
a .NET version of the AOT representing a Microsoft Dynamics AX Application.
When you use AX.NET to integrate with Microsoft Dynamics AX, you are actually working on
real .NET objects and enums, and thereby releasing all the productivity enhancing
features of Visual Studio, e.g. browsing through the AOT,
or providing Intellicense and auto completing, when writing code in Visual Studio.
All labels from Microsoft Dynamics AX are automatically placed on Enums and Tables and are available as documentation in Visual Studio.
AX.NET provides full support for labels in Microsoft Dynamics AX, and thereby making
it much easier to maintain localization.
Using AX.NET it’s possible to avoid having labels stored in both Microsoft Dynamics AX and
.NET, because all localization and labels can easily be handled by Microsoft Dynamics AX.
|