Question on AXModel files

(0) Share

Report

Posted on by Shashikanth Rao

575

I am coming from a .NET background where the code is distributed through assemblies which contain code that is interpreted by .NET CLR. Now I am doing some work on Dynamics AX 2012. I see that axmodel file is the way to distribute solution to customers. I have some questions regarding axmodel files. Can somebody please clarify?

1) What will be the contents of axmodel files? code that is interpreted (just like .NET assembly) or X++ source code itself?

2) How can I distribute my custom code or solution to customers with only interpretable code, just like we do in .NET assemblies?My intention is not ship any source code to customers.

Thanks in advance.

*This post is locked for comments

All responses (3)

Answers (1)

Dick Wenning 8,705 on at

Like (0)

Report

Re: Question on AXModel files

Your visual studio project gets embedded in the model. when the model is deployed your visual studio project gets exctacted at compile time. look at the server or client bin map you can see it,

X++ code is transvert to code that is stored on the aos. when an AOS restarts this code gets flushed to the Server\bin map and you have your X++ CIL code
Suggested answer

Joris dG 17,775 on at

Like (0)

Report

Re: Question on AXModel files

You can basically distribute .NET assemblies and reference them in the AOT. Of course you need to call them, too. So at least the reference and the call will have to distributed as an AxModel file.

As Martin said, the AxModel is all metadata, so yes source code as well as other AOT artifacts. But no compiled code.
Verified answer

Martin Dráb 230,445 Most Valuable Professional on at

Like (0)

Report

Re: Question on AXModel files

.axmodel files contain exported data from AX Model Store database. Installation of a model therefore means just adding new data (code, metadata) to the database and you have to compile X++, generate IL and synchronize AX database before the application can be used.

AX does not use any binary format for X++ - the code is always there and if customers has access to AOT, they can read the code. On the other hand, to decompile .NET assemblies is a piece of cake too.