Blue Iris Update Helper (BiUpdateHelper)
- Thread starter bp2008
- Start date
Getting closer! See my post above.
BiUpdateHelper.exe won't launch by double-clicking it because it is a service executable. As long as you have the service running, you've got it working correctly.
If this continues to be problematic for people, I will change things so that double-clicking the exe will open a service management GUI, and I'll get rid of the batch files.
If this continues to be problematic for people, I will change things so that double-clicking the exe will open a service management GUI, and I'll get rid of the batch files.
Woot! Thanks @bp2008! I'm already using your better web viewer and now this! Much appreciated. I'd go ahead and try the upgrade helper and see how it starts the archive but the current release apparently is not good.
Just checked and it's there. Thanks everyone!
bob2701
Getting comfortable
I've just released version 1.2 which no longer uses the batch files to control the service. Instead you can just run BiUpdateHelper.exe and a graphical interface will appear to deal with Install/Uninstall, Start/Stop.
Version 1.2.1 now, just with minor improvements to the GUI ... like it now shows the path to the currently installed service executable.
The core code is unchanged since version 1.1, so there is little reason to update if you already have 1.1 working.
The core code is unchanged since version 1.1, so there is little reason to update if you already have 1.1 working.
This does what I have been doing manually for a while except for one thing. I also make a backup of BI registry settings prior to updating. I've only used it once when a update fouled enough to require a complete fresh install. Could this be added to the "Helper" and saved along with the last update file?
Could you also backup the license key?
Thanks for the great BI add-ons!
Could you also backup the license key?
Thanks for the great BI add-ons!
I like that. I'll add registry backups, and the license key is part of the registry settings.
And a Configuration Backup prior to the update running?
bob2701
Getting comfortable
I just used a labeling machine and put the key right on the pc. Can't forget or lose it.
Version 1.3 released, including registry backups and BI registration key viewing functionality!
I noticed BI is saving a ridiculous amount of binary data in the registry now, so when I do a registry export it writes a 200 MB file!! So this program will automatically compress registry backups with 7zip. In 7z format, my 200 MB .reg file is only 106 KB.
A configuration backup is a registry backup. And I do have it coded to attempt a backup while the update downloads. It can also do daily backups just because, and manual backups too via a button in the GUI.
I noticed BI is saving a ridiculous amount of binary data in the registry now, so when I do a registry export it writes a 200 MB file!! So this program will automatically compress registry backups with 7zip. In 7z format, my 200 MB .reg file is only 106 KB.
Please note I have only tested this program with 64 bit Blue Iris on 64 bit Windows 10. If anyone has any problems, please specify:
1) Which OS you are using (Vista/7/8/10)
2) Whether the OS is 32 or 64 bit
3) Whether Blue Iris is 32 or 64 bit
It is possible that some portions of the program may fail with 32 bit Blue Iris or 32 bit Windows, and I can't fix the bugs if I don't know about them.
1) Which OS you are using (Vista/7/8/10)
2) Whether the OS is 32 or 64 bit
3) Whether Blue Iris is 32 or 64 bit
It is possible that some portions of the program may fail with 32 bit Blue Iris or 32 bit Windows, and I can't fix the bugs if I don't know about them.
bob2701
Getting comfortable
Can 1.3 be installed right over 1.1 or do you recommend uninstalling first?
No need to uninstall first. That is just an extra few clicks anyway. All you need to do is make sure BiUpdateHelper isn't running -- so the exe can be overwritten. So stop the service, extract/overwrite, and start the service again.
After you update, you can delete the .pdb file as I decided not to clutter up new releases with that file (its presence only provides line numbers in some error messages).
You can also delete the batch files (.bat), as their functionality is entirely replaced by the GUI you get if you open the .exe file directly.
After you update, you can delete the .pdb file as I decided not to clutter up new releases with that file (its presence only provides line numbers in some error messages).
You can also delete the batch files (.bat), as their functionality is entirely replaced by the GUI you get if you open the .exe file directly.
