Publishing Windows apps

Umajin Editor supports producing Windows standalone apps. Although we refer to this as “publishing” the end result is a normal Windows application that can be packaged and distributed however you like.

Codesigning requirements

For average users, Windows software should be signed with an Authenticode Code Signing certificate. You can buy these from many certificate vendors.

Note: Microsoft provide better “reputation” to Extended Validation certificates, which cost more but provide more thorough verification of your identity. This helps maintain your applications’ reputation through Microsoft’s SmartScreen services built into Windows and Edge. If you just use a regular certificate, each certificate renewal will reset your app’s SmartScreen reputation and it may be initially blocked with a warning.

To have Umajin produce an EXE signed by your certificate, upload the .PFX file and password into our Publishing wizard.

Alternatively, you can have your installer re-sign the EXE file with your code signing certificate.

Preparing publishing assets

For the most part, Umajin will package your project files as required. Some special files are involved, as below.

Icons and Splash Screen

For Windows apps these are simply files you add to your project in a specific location:

Icon: manifest/win/application.ico

Splash: manifest/win/splash.png or splash.jpg

Native libraries

If you have integrated native libraries (DLLs) into your app then they should be placed in the standard location:

DLLs: manifest/win/bin/

Publishing process

To begin, use Umajin Editor’s menu: File > Publish… and select Publish to Desktop.

Umajin Editor will save the project and then the process will continue in the cloud.

Cloud – Publish information

First, select the operating systems you want to target. In this case, select Microsoft Windows, and click Next

Cloud – Windows information

You will need to enter some details for Umajin to build your app.

  • Windows App Name: this will be used for the exe name, for the Window title at startup, and for the embedded version resources.
  • Version: this will be embedded inside the version resources

If you want Umajin to perform codesigning of the app for you, then you also need to fill in the following fields:

  • Codesign certificate: the .PFX file you bought from the certificate vendor
  • Codesign password: password for the PFX file.

If you don’t fill these in, then the app will be signed by Umajin.

Security Note: Your Codesigning certificate and password will be stored on our cloud servers, encrypted with a key that only Umajin is able to decode internally.

Click Next to save the data you have entered.

After entering data for any other platforms you want to distribute to (Mac, iOS, Android) you will reach the Confirm page.

Build process

Please contact Umajin to build the software after you have filled in the data above.

Packaging Output

Umajin will perform a basic packaging of your application into a zip file.

The zip contains the executable, various supporting DLLs, any native DLLs you have added, and the files from your project. These files can be changed after building if required.

You can run the application by simplying unzipping the file, and double clicking the EXE file.

You will probably want to package the app using a suitable branded installer. There are commercial options such as Advanced Installer and free options likeĀ NSIS.