How to prevent double installation? - Advanced Installer Community
MrZebulon
Posts: 7
Joined: Fri Jul 27, 2012 10:16 am

How to prevent double installation?

Hello All,

I've created 4 msi-packages.
2 languages, German and French and 32 / 64 bit.

Short example:
If the German msi in 32bit is installed, nevertheless I can install the French version.
Do I have to use one Product Code for all versions? and the same update-code?

many thanks in advance
Roland
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: How to prevent double installation?

Hello Roland and welcome to Advanced Installer forums,

Please keep in mind that Microsoft recommends to set a different product code for each language. Please take a look on "ProductCode property" article. Although it's not recommended, you can achieve this using the same product code for your both languages project.

If you want you can create a multilingual installation package for both languages. Go to "Translations" page, select the desired languages and enable "Create only a multilingual package" option. Also, you can take a look on the following articles:
- Other Languages
- New Language
- Show language selection dialog

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
MrZebulon
Posts: 7
Joined: Fri Jul 27, 2012 10:16 am

Re: How to prevent double installation?

Daniel.Radu wrote:Hello Roland and welcome to Advanced Installer forums,

Please keep in mind that Microsoft recommends to set a different product code for each language. Please take a look on "ProductCode property" article. Although it's not recommended, you can achieve this using the same product code for your both languages project.

If you want you can create a multilingual installation package for both languages. Go to "Translations" page, select the desired languages and enable "Create only a multilingual package" option. Also, you can take a look on the following articles:
- Other Languages
- New Language
- Show language selection dialog

All the best,
Daniel
Hey Daniel,

we bought the enterprise edition one week ago and I really like your product. It's amazing - but still a couple of bugs.
The dialog editor sometimes is a bit goatish.
I figgured out that the prepareDLG MUST exit with "close current dialog" and "RETURN" and not with "display a specific dialog" . Otherwise there is an errormessage with the FolderDLG. No "path defined" or so. At the first look there is no relation between this dialogs.
This cost me qite a couple of my nervs.
A redesign of the Dialog Editor to make it more usefull would be very great.
I like the dialog repository but for me its a bit stiff. Is "move to repository" the same as copy to repository.
Why can't I store my own dialogs no matter what kind of to use them in other projects? They are stored as xml. so it should'nt be a problem. My idea is something like a tex-module repository
like in ms-word or so.
What else I've noticed ist that the import of a msi-installer, even if it's made with AI doesn't import everything. Some dialogs are missing and some actions referring button object are missing.
Such as the prepareDLG's "Next" button has lost it's action. Nothing defined. And so on...The LicenseAgreementDLG and the ShortcutDLG are not imported at all.


But - carry on with the great work.
Kind regards
Roland
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: How to prevent double installation?

Hello Roland,
I figgured out that the prepareDLG MUST exit with "close current dialog" and "RETURN" and not with "display a specific dialog" . Otherwise there is an errormessage with the FolderDLG. No "path defined" or so. At the first look there is no relation between this dialogs.

I'm afraid I don't fully understand what you mean. Can you please give us more details about this (maybe exemplify)? Also, if there is a bug can you send us a test case?
I like the dialog repository but for me its a bit stiff. Is "move to repository" the same as copy to repository.
Why can't I store my own dialogs no matter what kind of to use them in other projects? They are stored as xml. so it should'nt be a problem. My idea is something like a tex-module repository
like in ms-word or so.
The "Move To Repository" option export a dialog in the Repository directory, so you have the possibility to use the related dialog in another project.
What else I've noticed ist that the import of a msi-installer, even if it's made with AI doesn't import everything. Some dialogs are missing and some actions referring button object are missing.
Such as the prepareDLG's "Next" button has lost it's action. Nothing defined. And so on...The LicenseAgreementDLG and the ShortcutDLG are not imported at all.
Please note that the import features in Advanced Installer (the Repackager, the Import MSI feature etc.) are intended to be used to get a starting point for your installation package, not to completely reproduce other installation packages. The Repackager tool captures only the effects of the installation (the changes made on the system). If the original installation package executes custom code (programs, scripts etc.) then only the effect will be captured (registry entries, files and folders etc.).
Also, after repackaging an installation some adjustments may be necessary in order to obtain a working installation package.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
MrZebulon
Posts: 7
Joined: Fri Jul 27, 2012 10:16 am

Re: How to prevent double installation?

Daniel.Radu wrote:Hello Roland,
I figgured out that the prepareDLG MUST exit with "close current dialog" and "RETURN" and not with "display a specific dialog" . Otherwise there is an errormessage with the FolderDLG. No "path defined" or so. At the first look there is no relation between this dialogs.

I'm afraid I don't fully understand what you mean. Can you please give us more details about this (maybe exemplify)? Also, if there is a bug can you send us a test case?


Hello Daniel,

Here are more deails and some screenshots.

1. Szenario

You see my sequenze of dialogs and the prepareDLG
Look at the pics.
Build and start the msi. result -> If you don't quit the prepareDLG's "NEXT"-button with Return, you'll have an error if you leave the licenseagreementDLG with "Next".

Kind Regards
Roland
Attachments
This fixes the error, see the red marked areas. The Next Button MUST be quit with RETURN, otherwise there is the error described.
This fixes the error, see the red marked areas. The Next Button MUST be quit with RETURN, otherwise there is the error described.
ai_Prepare_return1.png (118.2 KiB) Viewed 6790 times
This is the error message
This is the error message
ai_Prepare_error1.png (48.59 KiB) Viewed 6790 times
See the condition of the "Next Button" this causes the error if you leave the licenceagrrementDLG with Next
See the condition of the "Next Button" this causes the error if you leave the licenceagrrementDLG with Next
ai_Prepare_error2.png (83.64 KiB) Viewed 6790 times
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: How to prevent double installation?

The "PrepareDlg" dialog is briefly displayed at the beginning of the install process until searches and path resolution actions are performed. The installing user will never press its "Next" button and you should leave its default settings.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”