Artifact comparison
The following sections discuss the artifact comparison between Dynamics AX 2012 and finance and operations apps.
| Description | Dynamics AX 2012 | finance and operations apps |
|---|---|---|
| XPO | Yes | No |
| Models | Yes | Yes |
| Model store | Yes | Replaced with deployable package (only binaries) |
| Deployable package | No | Yes |
| Version control | Optional | Mandatory (Azure DevOps) |
| Automated build | Optional | Mandatory |
| Build deployment artifacts | XPO/Models/Model store | Deployable package |
| Lifecyle Services deployment | No | Mandatory |
| Microsoft hotfixes | Pick and choose knowledge base articles | Cumulative quality updates through Lifecycle Services |
| New release | Upgrade (code conflicts/data-upgrade) | Service updates through Lifecycle Services |
| ISVs | XPO/Models | Models/Deployable package |
In Dynamics AX 2012, you use XPOs to move code and share code. In finance and operations apps, XPOs are not available because you can no longer deploy source code. In finance and operations, code is deployed by using binaries. A software deployable package contains all models and binaries that you currently have in an environment. Consider a software deployable package as a single package that represents all non-Microsoft software in an environment. You can also consider a deployable package as pre-compiled code that can be used in a runtime environment.
Models are still used in finance and operations, though minor differences exist in how models are used. The model store concept has been deprecated; instead, deployable packages are used. Instead of using the model store, deployable packages are used for deployment that contains pre-compiled code that only contains your extensions or customizations. This feature makes builds quicker because you are no longer building the entire application, you are only building your code and extensions. Deployment is also faster.
You use Microsoft hotfixes for Dynamics AX 2012, and you can pick and choose knowledge base articles. finance and operations apps has a One version release policy. Continuous updates are mandatory through service updates in Lifecycle Services. Monthly updates are released eight times a year, and they are cumulative quality updates. Rather than picking and choosing knowledge base articles, you will get the latest quality build and consume it in your production environment after it has been applied and tested in sandbox environments. New releases are also applied in Lifecycle Services.
In Dynamics AX 2012, independent software vendor (ISV) solutions are delivered as XPOs or models. In finance and operations apps, customizations are shared as models if the ISV chooses to expose source code. If they are not exposing source code (binaries only), they will deliver a software deployable package that is ready to be deployed to your solution.