-
Notifications
You must be signed in to change notification settings - Fork 19
Testing Update Feature
You need to have two tools installed on your machine, in order to package the installer.
-
MSBuild 12.0 or higher. It comes with Visual Studio 2013, but can also be installed separately from here. The default location is
C:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild.exe - Nuget.exe, which can be downloaded from here
Make sure that both tool locations are in your PATH environment variables before packaging.
- Open the command line prompt. (Win+R, then type "cmd")
- Move to the
[Journaley project root]\Installerdirectory. Let's say that Journaley root is atD:\Journaley. Then type:
cd /d D:\Journaley\Installer
- Type in the following command to create the installer package with the current version. The ReleaseType can be one of three things: Stable/Develop/Local. For testing update feature locally, the "Local" option should be used.
D:\Journaley\Installer> MSBuild.exe Installer.proj /p:ReleaseType=Local
This command rebuilds, and creates the installer under [Journaley project root]\Installer\Releases. These files should be uploaded to the S3 bucket in the future.
When the installer is created for the first time, it only creates the full package. For all the subsequent packaging, it would also create the delta file relative to the latest existing installer package.
The ReleaseType option determines the update source location.
| ReleaseType | Update Source Location | Version Number Format |
|---|---|---|
| Stable | http://journaley.s3.amazonaws.com/stable | #.# |
| Develop | http://journaley.s3.amazonaws.com/develop | #.#.####.##### |
| Local | [Journaley project root]\Installer\Releases | #.#.####.##### |
First, create an installer using the appropriate ReleaseType option and install it. For local testing, use "Local" option.
When using the "Stable/Develop" option, upload all the files in the Installer\Releases folder to the "stable/develop" directory under Journaley S3 bucket. The "Local" option doesn't require this step.
Next, run Journaley using one of the shortcuts (in the Desktop / Programs) created by the installer. Launching the Settings UI and clicking the "Check for Update" button should say that "Journaley is already up to date!".
Now, create another version of the installer, using the above MSBuild command to create another installer with a bigger version number. Note that when using the "Stable" release type, this may not work unless the first two parts of the version number are manually changed in the source code.
When using the "Stable/Develop" option, upload the newly created files under Installer\Releases folder to the S3 bucket. Again, this step isn't necessary when testing with the "Local" option.
Then, run Journaley again using the previously installed shortcuts. It should now show the green dot with the settings button, and in the settings form, unless the auto update option is checked by the user.
All the update related features can be tested as described here.