The following table lists which programming model or models are best used in each development pattern.
Design Pattern | Programming Model | ||
| Strongly typed .NET interop to X++ | Services | Object-oriented development in X++ | |
| Customization | Use to access functionality implemented in X++ from .NET. Where appropriate, you should use eventing to decouple customization business logic implemented in .NET. | Not recommended | Layer-based X++ source code customization is supported. Where appropriate, you should use eventing to decouple customization business logic implemented in X++. |
Integration | Not recommended | Use service interfaces to access Microsoft Dynamics AX. | Not recommended |
External application development | Use if your Windows application runs only on the AOS server. | Use service interfaces to access Microsoft Dynamics AX in all other cases, including applications that are not Windows-based. | Not recommended |
Report development | Not recommended | Use service interfaces when implementing data methods as your report data source type. | Use when developing an RDP data source type for your reports |
Enterprise Portal application development | Use from Enterprise Portal applications to access business logic that is in X++ classes. | Use services to access Microsoft Dynamics AX functionality, especially if the application is Internet facing. | Not recommended |
No comments:
Post a Comment