Export (0) Print
Expand All

X++ Compiled to .NET CIL [AX 2012]

Updated: March 1, 2012

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

In Microsoft Dynamics AX, scheduled batch jobs written in X++ must first be compiled into the common intermediate language (CIL) of the .NET Framework. Therefore, X++ batches can sometimes complete much faster than if they were run as interpreted p-code.

NoteNote

An older name for CIL was Microsoft intermediate language (MSIL).

The basic steps for running X++ source code as CIL are described in the following table.

Step

Description

Write, save, and compile your X++ class.

The X++ source code for your class is automatically compiled into p-code when you save the source in the AOT.

Compile the p-code into CIL.

X++ is compiled into p-code. The p-code can be compiled into CIL by the following menu:

AOT > Add-ins > Incremental CIL generation from X++

Also, the toolbar on the development workspace has buttons for generating CIL.

TipTip
If errors occur during the generation of CIL, consider temporarily suspending the antivirus software that is running on your AOS computer. The CIL generation process writes files to an AOS installation subdirectory. The directory path could resemble the following: C:\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\bin\XppIL\

Recycle your multiple AOS services.

If your installation has more than one AOS, you must recycle every AOS service after the CIL build finishes.

The recycle causes each AOS to load the assembly that contains the updated CIL.

Global ::runClassMethodIL

You can run your X++ code as CIL by using the method ::runClassMethodIL. See the code sample later in this topic.

Run the X++ method with a batch job.

Batch jobs run only on the AOS, not on the AX32.exe client. X++ classes that run on the AOS are run as CIL, not as p-code.

In the AOT, create a simple job that calls your method. Schedule the batch job. For more information, see Walkthrough: Extending RunBaseBatch Class to Create and Run a Batch.

This section provides the X++ code for all the methods in a class that is named DemoClassCIL. You can create this class in the AOT.

The countNestedLoops method can be run by the X++ interpreter, or it can be run as CIL. The technique is to call the Global::runClassMethodIL method. This involves writing additional methods that wrap the countNestedLoops method. The method modifiers server static are necessary for this scenario.

The following countNestedLoops method is simple.

// Called by:  main, countNestedLoopsContainer.
public server static str countNestedLoops(int _numOfLoops)
{
    int runningSum = 0, ii, kk;
    
    for (ii = 0; ii < _numOfLoops; ii++)
    {
        for (kk = 0; kk < _numOfLoops; kk++)
        {
            runningSum++;
        }
    }
    return "Final sum is: " + int2str(runningSum);
}

Next, the countNestedLoopsWrapper method takes in a container as its parameter, and returns another container. This is the signature that is required by the Global::runClassMethodIL method. Notice this method is intended to be private, not public.

// Called by:  countNestedLoopsWrapper.
private server static container countNestedLoopsContainer(container _cNumOfLoops)
{
    int runningSum = 0, ii, kk;
    int numOfLoops;
    str sSumInString;
    container cReturn;

    numOfLoops = conPeek(_cNumOfLoops, 1);

    sSumInString = DemoClassCIL::countNestedLoops(numOfLoops);

    return conPoke(cReturn, 1, sSumInString);
}

Next, the countNestedLoopsWrapper method makes the call to the Global::runClassMethodIL method.

// Called by:  main.
public server static str countNestedLoopsWrapper(int _numOfLoops)
{
    container cFromCIL;
    
    new XppILExecutePermission().assert();
    
    cFromCIL = Global::runClassMethodIL
        ("DemoClassCIL",             // Or use classStr function.
        "countNestedLoopsContainer", // Or use staticMethodStr function.
        [_numOfLoops]
        );
    
    return conPeek(cFromCIL,1);
}

Finally we have the main method which initiates the run of the scenario. The main method calls the countNestedLoops and countNestedLoopsWrapper methods. The durations of each method are compared.

To run this method, open its source code in the MorphX client code editor, and then press F5 or click the green arrow icon.

// Run this method, from the MorphX code editor,
// or from a job under AOT > Jobs.
public server static void main(Args _args)
{
    int startTicksInterp, endTicksInterp;
    int startTicksCIL, endTicksCIL;
    str resultStrInterpreted, resultStrCIL;
    int numLoopsWanted = 987;
    
    // These first two calls ensure DLL files are loaded,
    // before we can do a fair comparison.    
    DemoClassCIL::countNestedLoops(numLoopsWanted);
    DemoClassCIL::countNestedLoopsWrapper(numLoopsWanted);

    startTicksInterp = WinAPIServer::getTickCount();
    resultStrInterpreted = DemoClassCIL::countNestedLoops(numLoopsWanted);
    endTicksInterp = WinAPIServer::getTickCount();

    startTicksCIL = WinAPIServer::getTickCount();
    resultStrCIL = DemoClassCIL::countNestedLoopsWrapper(numLoopsWanted);
    endTicksCIL = WinAPIServer::getTickCount();
    
    Global::info(strFmt
        ("%1 (Interpreted: %2), (CIL: %3).",
        resultStrCIL,
        endTicksInterp - startTicksInterp,
        endTicksCIL - startTicksCIL
        ));

/*** Infolog output:
Message_@SYS14327 (07:50:01 pm)
Final sum is: 974169 (Interpreted: 406), (CIL: 0).
***/
}

The Infolog message that is commented at the bottom of the main method shows that the CIL run completed much faster than the interpreted run.

Classes, tables, and enums are types in the X++ language. X++ types can be compiled to CIL. The queries and forms in the AOT are not X++ types, and they cannot be compiled to CIL. This means there are a few minor cases where calls from CIL to X++ p-code can cause an exception.

Suppose a method that is running as CIL calls a method on a query. The query method calls the ClassFactory system class of Microsoft Dynamics AX. This case causes an exception to be thrown. The problem is that the CIL session does not have access to all the system classes, yet the query method makes a call to a system class.

Your CIL code often cannot call query methods that call system classes. However, in Microsoft Dynamics AX some system classes have been re-implemented in CIL. These re-implementations enable some of the cases to succeed.


Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. get your copy at the MS Press Store

Community Additions

ADD
Show:
© 2014 Microsoft