Those who have worked to establish an automated build for a larger AX app have likely used or experimented with CombineXPOs.exe - a nifty tool for stitching a number of XPO files into one single, optimized XPO. Recognizing the importance and value of this tool, we're been working on making a new version of it available to you all.
Amongst the most significant improvements are:
We'll be writing more about using CombineXPOs later, but for now you can get the beta version of the "Microsoft Dynamics AX2012 Combine XPO Tool" here:
Does it encode VS projects into the XPO? (ie from a source control tree where VS projects are stored in native files - not XPOs)
Even if it does (we've tried it) it seems an XPO containing certain types of VS projects does not import properly through command line, only through the actual dialog inside AX?
The version control representation of Visual Studio files is their native format (csproj, cs, ...) and not XPOs. To build your application from version control you don't import them as you do with XPOs. Instead, you run msbuild in the projects directories (or load and build them in Visual Studio). This will create all the necessary build artifacts and push them back into the current AX layer/model.
If the visual studio projects are stored in XPOs (manual export from MorphX), you are right that CombineXPOs will not always be able to handle them and the build process becomes more complicated too as you will also have to perform the msbuild step on the extracted files.
Is there a certain process that is impacted by CombineXPOs not handling this?
I have only one XPO file. Do I still need to call CombineXPOs tool?
It is nice tool but after i get my individual XPo when i import it again i do not see the project of that xpo ,any idea ? !