

Now, we have created the GUI application MSI installer which can be distributed to other machines. “ Signing” – (optional) Only if you want to sign your application solution with your signed certificate.Īfter everything under setting has been configured, proceed to “ Build” the installer. You can add more resource file with it.Ĥ. “ Files/ Folder” – This section will set where your MSI files will be stored. Notice you can chose any PowerShell version available.ģ.

Under “ Product Details” – Describes your application in details. “ Deploy | Installer” – “ Settings” – To enter all the information needed about this GUI application.Ģ. The flow to build your MSI installer would be:ġ.

In our previous blog we build a GUI application and created the executable file using either the “ Build” or “ Build & Run” option under the “ Deploy | Packager” section.Īlthough, this is optional, we could have created an MSI installer which will produce all the necessary steps to deploy the GUI application.
