Make Windows Executables: Difference between revisions

From NSB App Studio
Jump to navigation Jump to search
No edit summary
No edit summary
Line 5: Line 5:
# If Preferences are set to 'Deploy to local folder', the exe file will be in that local folder.
# If Preferences are set to 'Deploy to local folder', the exe file will be in that local folder.


3 Otherwise, the exe file be in a folder named with the project's ID in the project folder.
# Otherwise, the exe file be in a folder named with the project's ID in the project folder.


Notes:
Notes:

Revision as of 19:32, 17 April 2015

Make Windows Executable makes an exe installer file from your app. It can be redistributed to other users with Window system.

To run it, use Make Windows Executable (exe) App on the Run menu. A few seconds later. the exe will be produced. Depending on your settings in Preferences, it will be in one of two places:

  1. If Preferences are set to 'Deploy to local folder', the exe file will be in that local folder.
  1. Otherwise, the exe file be in a folder named with the project's ID in the project folder.

Notes:

  • All the files in the project folder get included in the exe file. It's best to keep your app in its own folder, and to keep it tidy.
  • The default size of the window at runtime is the project's defaultformsize property.
  • The version, copyright and title are all taken from your project's properties.

It works by packaging your app with a Windows runtime wrapper. InnoSetup (built into AppStudio) is then used to make a full Windows installer. Running it will install your app into Program Files and add it to the Windows Start menu.

At runtime, it uses the Internet Explorer 11 engine. Users will need to have this installed to run apps.