| Author |
 Topic  |
|
|
esse
3 Posts |
 Posted - 10/26/2009 : 04:55:31
|
Hello,
we'd like to update multiple products wich belongs together and are located in the same base dir, with AutoUpdate+. Therefore the updater should take care of stopping and starting every particular Exe. Is it possible to build a global update.exe to make sure that the update prozess is, let's say like a transaction (all or nothing).
Is something like this possible with Autoupdate+.
We use AutoUpdate+ 3.8 at the moment, but we'd like to upgrade to the latest version.
Thanks in advance
Marko Espig
Ibykus AG
|
|
|
SimonEllis
Australia
183 Posts |
Posted - 10/26/2009 : 17:43:12
|
| AutoUpdate+ v3.8 is quite an old client. I believe we can do what you require with the v5.0 client, and you can look into purchasing an upgrade license to that release. I will send you an email to discuss the details... |
 |
|
|
esse
3 Posts |
Posted - 10/27/2009 : 05:29:37
|
Hi Simon,
we evaluated the v5.0 Client. There are some issues that i wanna let you know of. First of all there are some graphical problems with the AUTool.exe always reported by my collegue. I realized that there is no CRC Check anymore, as in v3.8, so files are always downloaded even if they are "up to date", if I'm not using the incremental update. Am I right ? I know that the incremental update would be a solution for this, but im not sure if we want to reorganize the update project for every release.
Usualy we only replace the files for the whole thing and rebuild the project.
In the v5.0 Deployment there is a terminate section, which is exactly what we need for the multi product update, I already tested it. But we need to remember which exe was terminated to restart it at the end of update. I guess it is easier for you to implement such functionality in the application, as you know which exe you had terminated, as if I would write some script to do that. We think about something like a checkbox at the "Add Termination Dialog" like "RestartIfWasTerminated".
Can you tell me something about purchasing and pricing for the upgrade and the additionally functionality.
Best regards
Marko
|
|
|
|
SimonEllis
Australia
183 Posts |
Posted - 10/27/2009 : 19:19:34
|
> graphical problems with the AUTool.exe
Can you please send me a screenshot by email, and a note of the OS where this problem is seen. Any details to explain when/how this issue pops up would be great.
> there is no CRC Check anymore, as in v3.8
Correct. This change occured quite a while ago. You may want to search through the forum for details as to why we made this change, as I think this issue has been raised before.
> we need to remember which exe was terminated to restart it at the end of update. I guess it is easier for you to implement such functionality in the application
We may be able to automate this step for you. If it's a serious issue that needs immediate attention then we can support it via custom programming (usually at lower rates than you would incur in putting together your own fixes). If it's not a critical issue then we will need to add it as a feature request for future releases.
> Can you tell me something about purchasing and pricing for the upgrade
I am not sure of the licensing status of your company. We always send out a link to renew the purchase 1 month before the license expires. If your license has already expired, which I assumed is the case if you last used v3.X (quite old), then you will need to purchase a new license directly from our site: http://autoupdateplus.com/Register.html
|
|
|
|
FHofmann
5 Posts |
Posted - 12/14/2009 : 03:44:43
|
Hi Simon,
as u probably know i'm working for the same project and company as esse.
We just renewed our licence and it seems that the graphical problems don't occur with the new client.
Although ur product is at a high level, we still have a request:
- would it be possible to create a third option that does "create if parent dir exists" (maybe even for subdirs)?
Background: the user is able to install modules that should only be updated if the user had installed them. So even new files should only be deployed if their directory exists on the target platform. I think this feature will take ur product a step ahead to support complex software projects which are combined of different sub packages... |
Edited by - FHofmann on 12/14/2009 08:51:44 |
|
|
|
SimonEllis
Australia
183 Posts |
Posted - 12/15/2009 : 17:41:07
|
Hi,
Thanks for the feedback. All customer feature requests we receive are ranked by: 1) Complexity to implement. 2) Ability to resell idea to other customers. I will add this feature request into our database. If it's something that's critical and you wish to have it implemented ASAP, then please send us an email about custom programming -- we offer customizations as high priority requests, and these can be done at much lower costs than you would achieve with your workaround scripts/tasks.
Regards,
Simon |
|
|
|
FHofmann
5 Posts |
Posted - 07/14/2010 : 02:38:15
|
Hi Simon,
are there any plans to implement a feature 'create if parent dir exists' as mentioned above?
best regards,
frank |
|
|
| |
Topic |
|
Mutli Product Updates
