HowTo: Deploy Front-end applications to a Cloud Provider Object Storage

Official Content
This documentation is valid for:

This article shows you the steps to deploy your front-end application to a Cloud Provider Object Storage. To do so, you can use the Application Deployment tool from inside the GeneXus IDE or Msbuild commands.

Deploy using Application Deployment tool inside GeneXus

1. In GeneXus, go through the "Deploy Application" contextual menu option after having created the Deployment Unit object containing the main objects of your app


2. Select the "Static Front end" option from the Targets combo box.

3. From the Properties dialog, select a Front-end Deployment target (AWS S3, or Azure Blob Storage).
Depending on the target selected, you have to enter different options.
4. Finally, press the deployment button.


If you wish, you can just create the deploy package by checking "Only Package". In this case, you will have the package under the Deploy\STATICFRONTEND\<DeploymentUnit> directory of the KB.

MSBuild tasks to deploy to a Cloud Provider Object Storage

The Application Deployment tool is based on MSBuild tasks. Using those tasks, you can automate deployment.

In the case of front-end applications, three MSBuild scripts are executed to perform the deployment.

1. Create FrontEnd Project

GeneXus provides a script called deploy.msbuild (located at the root of the GeneXus installation) which is used to create a deployment project for front-end applications, when the Target deployment (TargetId) is "STATICFRONTEND".

This step creates a file called <ProjectName>.gxdproj (an MSBuild script) which contains a list of the selected objects of the Deployment Unit object, and some environment properties for the deployment. This gxdproj file is used as input of the MSBuild task that deploys to the cloud.

Properties to add to the MSBuild execution:

  • DEPLOY_TARGETS: Reference to .targets file where the validations are implemented (staticfrontend.targets).
  • KBPath: Path to the Knowledge Base
  • KBVersion: Name of the version to be set as active
  • KBEnvironment: Name of the environment in that version
  • DeploymentUnit: Name of the deployment unit
  • ProjectName: Name of the generated .gxdproj file. By default, it is "DeploymentUnit_<TimeStamp>.gxdproj".
  • ObjectNames: Names and types of the objects to deploy (deployment units can also be selected) (ref: How to specify an object list in a MSBuild task). This parameter is optional if you specify the DeploymentUnit property.
  • Outputpath: Where the .gxdproj is saved. The gxdproj file is saved under $KB.Location$\$Model.TargetPath$\web if Outputpath is not defined. 


C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /noconsolelogger /nologo /logger:DeployLogger,"C:\Development\Trunk\Genexus\GeneXus.Deploy.MSBuild.Tasks.dll"
/verbosity:quiet /ToolsVersion:4.0 "C:\Development\Trunk\Genexus\deploy.msbuild"

2. Create Package

The build of the project is triggered by the CreateFrontendPackage.msbuild script, which receives the parameters explained below.

  • GXDeployFileProject: The path to the .gxdproj file generated in the "Create FrontEnd Project" step (including the name of the file). 
  • ProjectRootDirectory: The path to the directory under the KB, where the Angular application is generated (it is always under the mobile\Angular folder). E.g: "C:\models\TestAngular\TestAngular\NetSQLServer005\mobile\Angular"
  • GenExtensionName: The name of the front end generator (e.g.:Angular)
  • DeploymentScript: Each Frontend generator should have its own script for packaging (building the application). This should be specified at the DeploymentScript msbuild property.
  • GX_PROGRAM_DIR: GeneXus program directory.


C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /noconsolelogger /nologo /logger:DeployLogger,"C:\Development\Trunk\Genexus\GeneXus.Deploy.MSBuild.Tasks.dll" /verbosity:minimal /ToolsVersion:4.0 "C:\Development\Trunk\Genexus\CreateFrontendPackage.msbuild" /p:GXDeployFileProject="C:\models\TestAngular\TestAngular\NetSQLServer005\web\DeploymentUnit1_20220614182207.gxdproj"
Note: In the case of Angular, the DeploymentScript is "deploy.angular.msbuild" and is declared at the angular.generator file. The deploy.angular.msbuild is located at GenExtensions\SmartDevices\Angular\deploy under the GeneXus installation.

3. Deploy to the Cloud Provider

The solution to deploy the front end of an application is extensible and available at Github (StaticFrontEnd deployment target). Those files are in your GeneXus installation, under the DeploymentTarget folder.

There's a built-in solution for deploying to AWS S3 and to Azure Blob Storage. 

In this step, the application is built and everything is set up for distribution.

It has a deploy.msbuild script which includes the .target file depending on the STATICFRONTEND_PROVIDER property value (it can be "aws3" or "azureblobstorage"). Depending on the Provider, different properties are needed in order to deploy to that cloud.

For details on how to execute this step, see HowTo: Deploy Front-end applications to Azure Blob Storage.

Temporal Limitation

At the moment, only one main object must be deployed to each Storage.


Since GeneXus 17 Upgrade 9

See Also

Consider that in most cases you have to configure the CORS. See the following for more details:
HowTo: Deploy Angular front end applications using serverless backend