Concise Updater Tutorial in pdf format? - Advanced Installer Community
BillD
Posts: 18
Joined: Thu Apr 24, 2014 9:10 pm

Concise Updater Tutorial in pdf format?

Hello,

I am new to Advanced Installer. We chose this product because VS2013 support for Click-Once is gone, so I have been struggling to create an Updater project that silently installs updates. I find that going back and forth between web pages, AI, my project, my folders, etc., is getting ridiculous. Does anyone know if there is a downloadable pdf that describes (with project samples) how to make the Updater work? I suppose I can resort to deploying major upgrade installers for users to click on. It would be nicer, though, to have the silent installs when the applications are started up.

Regards,

Bill Dickinson
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Concise Updater Tutorial in pdf format?

Hello Bill and welcome to Advanced Installer forums,
I have been struggling to create an Updater project that silently installs updates.
In your main installation package will you need to configure the updater as it is described in the Handle updates without elevation article and further updates will not require any elevation because the support service which will handle updates without elevation is installed. The installation of this service  prepares the package to support the installation of updates without elevation on restricted user accounts.
Does anyone know if there is a downloadable pdf that describes (with project samples) how to make the Updater work?
If at any time you need more information regarding the current dialog or page functionality in the Advanced Installer GUI, simply press F1 and the corresponding help article will pop up.
We don't have a PDF format for the UserGuid, but we intend to create a PDF format also. Thank you for your suggestion. Until then, you can use a tool that converts a CHM to PDF.

Maybe, our Auto updates for non Admin users forum thread which contains a sample that implements this scenario, install updates without elevation can help you.
It would be nicer, though, to have the silent installs when the applications are started up.
In order to achieve that, you can select the Automatic: using a Windows scheduled task option for the Updater Execution from the Updater page and a Windows scheduled task will be created for Auto Updater executable file. Click [ Configure Task ] to specify the scheduled task's behavior.

Should there be any difficulty you encounter implementing something, please do not hesitate to contact me and I will gladly assist.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
BillD
Posts: 18
Joined: Thu Apr 24, 2014 9:10 pm

Re: Concise Updater Tutorial in pdf format?

Thanks Dan for your reply. I am following the tutorials and so far I have done this:

1. Create initial professional AI installer (named UpdaterTest.aip) for a C# Winforms project (very simple one, just to get started) named UpdaterTest.sln.
2. Add Updater to this project specifying the location of the update config file. Build and install application (UpdaterTest.exe).
3. Create a new AI Update project for the project created in step 1 named UpdaterTestUpdateConfig.aip.
4. I chose to add the update logic within the executable (using the C# example) for silent updates but I also added a button to check for updates and a button to edit the update config settings so I could test this manually. At this point, checking for updates says that the software is up to date, which I expect because I have not applied any updates yet.
5. Change button and form colors and change the version in C# project UpdaterTest.sln.
6. Change product version from 1.0.0 to 2.0.0 in Updatertest.aip, save, and rebuild. New installer is renamed UpdaterTest2.0_x86_Debug.exe
7. Add an update to UpdaterTestUpdateConfig.aip, point to UpdaterTest2.0_x86_Debug.exe, save and build, and copy config file to the location specified in step 2.
8. Fire up UpdaterTest.exe - no version change shown; checking for updates by clicking the button says the software is up to date.


So, I am obviously missing something. Can you suggest where I went wrong? Thanks.

Bill
BillD
Posts: 18
Joined: Thu Apr 24, 2014 9:10 pm

Re: Concise Updater Tutorial in pdf format?

Would it help if I provided copies of my projects?

Bill
BillD
Posts: 18
Joined: Thu Apr 24, 2014 9:10 pm

Re: Concise Updater Tutorial in pdf format?

I think I got it to work by revising the entry in the updater.ini file to point to the correct location of the updates.txt config file. Will continue testing...

Bill
BillD
Posts: 18
Joined: Thu Apr 24, 2014 9:10 pm

Re: Concise Updater Tutorial in pdf format?

I finally got the manual update to work using a "Check for Updates" button which fires of the updater.exe in the background. I have found that there are lots of ways to shoot your self in the foot because so many things need to be changed before an update is detected:

1. Update assembly version (to use registry changes for update detection)
2. Update the project version to match the assembly version (to trigger a major upgrade)
3. Retype the location on the network share of the update installer in the update project - adding an update defaults the location to http://www.examples.com. In my case, I have to change the location to the installer file on the network share even after selecting the specific installer file from the selection dialog. It always comes up with the prefix www.examples.com.

In the end, you need an installer project for your solution AND and updater project for updates. Seems these two should be integrated since each depends on changes to install parameters related to the original solution (my C#_project.sln). I can live with this now that I know how I have shot myself in the foot.

However, I haven't gotten the silent install to work yet. Still trying Checking manually for updates (and installing them) and editing config settings work.
BillD
Posts: 18
Joined: Thu Apr 24, 2014 9:10 pm

Re: Concise Updater Tutorial in pdf format?

3. Retype the location on the network share of the update installer in the update project - adding an update defaults the location to http://www.example.com. In my case, I have to change the location to the installer file on the network share even after selecting the specific installer file from the selection dialog. It always comes up with the prefix http://www.example.com.
This appears to be a bug. When you are given the option of selecting an installer on a file share, the location should be retained after selection is made and the dialog is closed. Instead, the selected file is prefixed with "www.example.com"

Return to “Building Installers”