The X++ proxies are more dynamic than service proxies: Visual Studio will build the proxies anew every time a build takes place, so that “stale” proxies never become an issue.
#Morphx and the application object tree code
This richness is provided by using managed proxies to access the X++ code artifacts (classes, tables, and enumerations): The Microsoft Dynamics AX proxy concept is similar to the proxy concept that Visual Studio provides for consuming web services: The consumer does not see all the complex plumbing that takes place under the covers to make the interoperability happen, either with the X++ objects or with the service implementation.
#Morphx and the application object tree full
Managed developers are entitled to an editing experience where the X++ artifacts they interact with appear as just another set of full fidelity managed objects, with the convenience of documentation comments and full type safety. To use this functionality, you must have installed the Microsoft Dynamics AX Visual Studio tools. It is built with proxies and the Business Connector. Such a system is provided with Microsoft Dynamics AX and its integration with Visual Studio 2010. It does not provide a compelling story for building interesting business logic in managed code: For that you need a system that can seamlessly crisscross the boundaries between X++ and managed code. Using managed code from X++ as described above is certainly useful, but it is not the complete story. System.IO.File::Copy(fileName, newFileName, overwrite) Public client static boolean copyFile( str fileName, str newFileName, boolean overwrite = false) The following X++ code shows how a managed API can be used from X++: You can use managed APIs from assemblies that are added to the references node in the AOT, or you can author the code in a managed project that is hosted within the AOT: In the latter case the C# or VB source code and the project definition is available for editing directly from within the Microsoft Dynamics AX IDE. The lifetime of the objects is managed by the. NET types are distinguished from X++ types by using the full name of the managed type, including the namespaces. In other words, you can create and use objects of managed types from within X++ code quite seamlessly.
The X++ language embraces managed objects as first class citizens. The Microsoft Dynamics AX tools are integrated with this environment, allowing you to use all the features within that framework. As most C# and VB.NET developers would expect, this development takes place in Microsoft Visual Studio ® 2010, Microsoft’s premier multipurpose extensible IDE. In addition to the features provided by the X++ stack as just described, it is possible to author business logic in either C# or Microsoft ® Visual Basic ® (VB).NET. The X++ language is hosted within the MorphX IDE that contains everything needed for successful development work: debugger, code profiler, tracing tools, and so on. A pivotal part of this environment is the X++ language that was created specifically to implement large scale ERP systems where efficient data manipulation is of paramount importance. The Microsoft Dynamics AX Integrated Development Environment (IDE) features a rich environment that was specifically designed to provide a Rapid Application Development (RAD) environment for writing business applications. This requirement can be satisfied in two ways: by using the X++ language and by using managed languages. However, there will always be a need to perform computation to provide the required functionality. The system is model-based and much can be achieved by describing the expected functionality by editing metadata in the Application Object Tree (AOT). The Microsoft Dynamics ® AX environment features a rich palette of options for the business application developer.
0 kommentar(er)
