Deployment Instructions Screen (Magic xpa 4.x)
The Summary screen provides directions for deploying the configuration files and folders.
If the build of a platform fails, this will be noted in the Deployment Links section of the screen. In this case, you should check the build.log file in the platform's destination folder.
For the Windows desktop, the deployment of Rich Internet applications in Magic xpa is done using ClickOnce. The Rich Client Deployment Builder creates two configuration files:
-
Published Web Page – An HTML file, publish.html, that includes the application execution properties, such as the application name and the program to start. This file also includes links to prerequisites.
The HTML file contains a link to install the .NET framework. If you install the .NET framework using this link, you need to make sure that the Web alias has the proper permissions (in some cases, having the Execution permission will prevent the .NET framework from being installed).
Note: When using the GigaSpaces middleware, you need to manually change the requester path in the publish.html file.
Note:
-
You should always re-create the manifest files when upgrading the Magic xpa engine.
-
The Rich Internet application cannot be deployed using ClickOnce from a Guest account.
-
If you want to use ClickOnce with a project that is running from the Studio, you need to set the Deployment Mode to Background.
The Rich Client Deployment Builder creates an execution.properties file in the RIAModules\Android\source folder or the RIAModules\iOS\source folder.
You should place the files and folders on the application alias on the Web server, as defined in the Rich Client Deployment Builder.
