We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

gardea
Posts: 8
Joined: Fri Jul 18, 2008 4:29 am

Current user/Local machine and Auto updater

I tag the installed version with a registry key; it may go under current user or local machine, depending on the type of install.
How would I check for that in the auto updater, since it seems to only allow one registry key to look at?
This is a problem with limited rights users, who can only install per user.

Thank you.
dms
Posts: 164
Joined: Tue Aug 28, 2007 7:11 am
Location: UK

Re: Current user/Local machine and Auto updater

The fact that a limited rights user is doing the install shouldn't prevent you from placing a single registry key somewhere that can be accessed by any user.

Dom
gardea
Posts: 8
Joined: Fri Jul 18, 2008 4:29 am

Re: Current user/Local machine and Auto updater

You're missing the point; I do not want to have a single key for all, if the install was done per user - it defeats the purpose of why it was selected/allowed per user to begin with!
The question still stands: can autoupdater support more than one registry search(like the installer does) to establish a version #? If not, maybe quickly add support for a list using some sort of separator in between paths, as an interim solution?
dms
Posts: 164
Joined: Tue Aug 28, 2007 7:11 am
Location: UK

Re: Current user/Local machine and Auto updater

So are you in effect saying that there may be an occassion where your product is installed by different users on the same machine and you require the ability for the auto updater to offer each user the ablity to update the application if they so wish, but it doesn't matter if one does and the other one doesn't.

I'm not trying to be deliberately obtuse here, just trying to understand exactly what your policy with regard to updating your application is and why you so specifically wish to differenciate between current user and local machine. Knowing that might help to come up with a solution that works for you and falls within the confines of the auto-updater as it is currently configured.

Dom
gardea
Posts: 8
Joined: Fri Jul 18, 2008 4:29 am

Re: Current user/Local machine and Auto updater

I could not have said it clearer than you. To me the problem seems to be the asymmetry between how one can work with the registry: an installer project allow for a Current user/Local machine whereas an autoupdater project doesn't. In the autoupdater would implement a registry search where I could first try the current user then local machine, I would be all set. By the way, thank you for your help.
dms
Posts: 164
Joined: Tue Aug 28, 2007 7:11 am
Location: UK

Re: Current user/Local machine and Auto updater

Well it's not ideal but one way that you might well be able to achieve what you want would be by using the file option rather than the registry. I haven't had time to play with this idea and therefore verify that it would work, but theorectically it might, equally of course it might not!!

A specific file presence in say the all users application data directrectory might give you the equivalent of a common registry key in the hkey local machine hive with the added benefit that it should be accessible by all. It may even be that you could restrict it to the [appdir] but that really depends on how you install your app in the first place.

Dom
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Current user/Local machine and Auto updater

Hi,

Indeed, using a file is a good solution when you don't know if the package was installed per-user or per-machine. Unfortunately the Updater doesn't support multiple registry entries for the detection criteria. However, we will consider adding this improvement in a future version. Thank you for your suggestion.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
gardea
Posts: 8
Joined: Fri Jul 18, 2008 4:29 am

Re: Current user/Local machine and Auto updater

I don't see this working. How would the file search only for the current user? And then fall back to another "machine" location.
Would it be quickly if you just add support for autoupdater to be able to invoke an external dll ?
A .net assembly would be ideal, but I can live with an unmanaged one, too.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Current user/Local machine and Auto updater

Hi,
I don't see this working. How would the file search only for the current user?
You could install a file specially for the update detection in a per-user location (for example a folder in "Application Data"). When then user checks for updates, the Updater will always search in the per-user location.
Would it be quickly if you just add support for autoupdater to be able to invoke an external dll ?
We will consider adding this improvement in a future version of Advanced Installer. Thank you for your suggestion.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
gardea
Posts: 8
Joined: Fri Jul 18, 2008 4:29 am

Re: Current user/Local machine and Auto updater

And if the file is not found per user, will the search fall back to the per machine location?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Current user/Local machine and Auto updater

Hi,

No, this is not supported by the Updater. Also, the approach I mentioned uses only a per-user location (a per-machine location is not necessary). The package can use the self-healing feature to install the file to new users which login.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
gardea
Posts: 8
Joined: Fri Jul 18, 2008 4:29 am

Re: Current user/Local machine and Auto updater

Now, I am confused. If the intall is done per machine, how would I be supporting this scenario with a per user file??
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Current user/Local machine and Auto updater

Hi,

Please note that per-machine installations can write in per-user locations. For example, you can have two scenarios:
1) A per-machine installation:
- application files are installed in "Program Files"
- the update detection file is installed in "Application Data"

2) A per-user installation:
- application files are installed in "Application Data"
- the update detection file is installed in "Application Data"

When this is combined with the self-healing feature, the user which checks for updates will always have the update detection file in "Application Data". This file can be a simple Readme or help file or even a configuration file. The Updater can use its size to determine if an update is installed or not (supposedly the size of the file is changed in each new version).

Basically, no matter what installation type is used, you can install a per-user file which will be available for each user.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”