Table of contents

Official Content

The  Application Deployment tool is based on MSBuild Tasks, which allow you to easily extend and/or customize your deployments. Using those tasks, you can automate deployment.

The following document lists those tasks and details how to use them in order to either extend what GeneXus does or automate your deployments.


The CreateDeployProject task will analyze what GeneXus objects must be included in the deployment based on the call tree of every selected object (or every main object if none). The output of this task is an MSBuild script with the extension .gxdproj that will hold every environment property and object (with its properties) needed for a successful deployment.

GeneXus provides a script called Deploy.msbuild (located at the root of GeneXus installation) which is used by GeneXus itself and it's a great starting point for automating your calls. Use the following command to create a deployment project of every main in your Knowledge Base.

msbuild.exe <GX Installation directory>\deploy.msbuild /p:KBPath=<Path to your Knowledge Base>

This will create the deploy project (.gxdproj) file for the trunk version of the mentioned Knowledge Base for every main object in that version. There are a few properties you can add to change this behavior.

KBVersion: The name of the version to set as active

KBEnvironment: The name of the environment in that version

ProjectName: It will be the name of the generated .gxdproj file. If you leave this parameter empty, the DeploymentUnit parameter is taken to give a name to the gxdproj (concatenated with a timestamp value). If both, ProjectName and DeploymentUnit are empty, the name of the gxdproj will be "MSBuildDeployment" concatenated with a timestamp.

ObjectNames: The names (with their types) of the objects to deploy (deployment units can also be selected) (ref.: How to specify an object list in a MSBuild task). If you leave this parameter empty, all the main objects of the KB are included in the deployment.

APPLICATION_KEY: The new encryption key to set for your deployed application


TARGET_JRE: (Java only) the version of the Java runtime where the deployed app will run. (Default is 9)

PACKAGE_FORMAT: (Java only) whether the engine must create a WAR or an EAR. (Default is 'Automatic', the engine decides based on the selected objects)

SelectedObjectsOnly: When set to True the deploy engine will not calculate the call tree of selected objects. Only the selected ones will be deployed.

TargetId: Default will be "Local", but you can set any of the supported Deploy Application Targets.

SourcePath: Defaults to the KB directory\model. The gxdproj file is saved under <SourcePath>\web if Outputpath is not defined.

Outputpath: Where the .gxdproj is saved. 

You can also use the CallTreeLogFile property to get a log of the objects call tree.


MSbuild.exe /nologo /verbosity:minimal /ToolsVersion:14.0 "c:\GeneXus\deploy.msbuild" 
/p:ApplicationServer="IIS8" /p:TargetId="Local" 

The generated .gxdproj file is another MSBuild script which contains the needed info to create the packaged application.


To generate the package (it can be a zip file in case of C# and .NET Core or a war/jar/ear in case of Java), you need to execute the generated script as follows:

msbuild.exe <Full path>\MSBuildDeployment_20190123103151.gxdproj

In this case, you can also set properties to tell the engine where the generated package will be deployed.

DeployFullPath: Full path to which a copy of packaged files will be copied to. You can use this path to compare different deployments.

Take a look at the generated .gxdproj file to see the defaults for DeployFullPath and DeployFileFullPath properties.

    <!-- Destination paths -->

Deploy to external targets

GeneXus can also help you deploy to any of the supported cloud providers (deployment targets).

Every supported target is listed under the DeploymentTargets folder under the GeneXus installation. All of these targets have a deploy.msbuild file with a default task called Deploy


MSBuild.exe /nologo /verbosity:minimal /ToolsVersion:4.0 "c:\GeneXus\DeploymentTargets\Docker\deploy.msbuild" 

In sum, when the target is not local, the execution is in the following order.
Now, take AWSECS as an example.

1. The task CreateDeploy of the script deploy.msbuild of the GeneXus root is executed by msbuild, to which the Target Id and the deploy targets must be passed as properties, eg:

MSbuild.exe /nologo /verbosity:minimal /ToolsVersion:14.0 "c:\GeneXus\deploy.msbuild"
/p:AppName="DeployNet16" /t:CreateDeploy

As a result, the gxdproj file is obtained, where you will see the DeployTarget (TargetId information) and DeployTargetTask (DEPLOY_TARGETS information) properties.

2. The task CreatePackage of the gxdproj generated scripted is executed via msbuild. As a result you get a package on the local machine.

3. The Deploy task of the deploy.msbuild (located under <GX>\DeploymentTargets\AWSECS) is executed to deploy to the Paas.


Generate the GeneXus Log when you deploy using the Application deployment tool inside de GeneXus IDE, in order to see in the log, the msbuild tasks that are executed.

See Also

MSBuild Tasks
Team Development MSBuild Tasks
Application Deployment tool
How to specify an object list in a MSBuild task

Last update: November 2023 | © GeneXus. All rights reserved. GeneXus Powered by Globant