Build and execution core Foundation

A CXP (*.cxp or *.layout) file is automatically compiled at runtime when the view (URL ending with .cxp) is requested by the client, typically by a browser. Of course, compiling must be done only the first time the view is requested. Future requests just load the DLL and execute the code inside it. It is even possible to configure CXP so that multiple view requests are serviced by the same cxp-worker process, hence avoiding the overhead of loading of the DLL. This leads to super-fast view delivery times.

The cxc-builder is used to perform the CXP build process. The table below lists all files which are created during the transpile/compile/link cycle of the cxc-builder.

Note: *) CXP does not use the name of your CXP page as the name of the class. Instead the filename is mangled and extended with a timestamp. This is required to allow CXP to load different versions of the page at the same time.

You can find these files under the .\cxp-application directory. By default, all files except the DLL are cleaned up automatically. To avoid deletion, add the following XML markup to your global.config file in the root directory of your website.

<buildmanager> 
<behaviour trace="yes" clean="no"/> 
</buildmanager> 

The following are some best-practice rules for analyzing errors in the CXP build process.