MSI should start always "normal"
Hello experts,
I'm having the following problem with a MSI package.
I added a custom action, which controls an entered serial number and enabled modules based on the serial number. If I start the setup again the setup should start in the same way, if it had not been run since that moment. Since if it doesn't the setup is starting in the repair mode and only selects the modules which are already installed and not the new ones.
And the enduser has to check all new modules by himself and that should not be necessary.
The cutom action is a C dll and returns a value for each module, which sets the install level to 0 if the module should not be installed.
Is there any way to make sure that this is working?
thanks for your feedback
best regards
Mike
I'm having the following problem with a MSI package.
I added a custom action, which controls an entered serial number and enabled modules based on the serial number. If I start the setup again the setup should start in the same way, if it had not been run since that moment. Since if it doesn't the setup is starting in the repair mode and only selects the modules which are already installed and not the new ones.
And the enduser has to check all new modules by himself and that should not be necessary.
The cutom action is a C dll and returns a value for each module, which sets the install level to 0 if the module should not be installed.
Is there any way to make sure that this is working?
thanks for your feedback
best regards
Mike
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
nheim
17 years ago
Hi mike,
why do you start the setup again? Can't see the reason for this.
Have a look in the log file to see whats going on exactly.
This could be a sequence problem. That means the needed properties are not set early enough to get changed state over.
Hope this gives you some ideas.
Regards, Nick
why do you start the setup again? Can't see the reason for this.
Have a look in the log file to see whats going on exactly.
This could be a sequence problem. That means the needed properties are not set early enough to get changed state over.
Hope this gives you some ideas.
Regards, Nick
Posted by:
bikersani
17 years ago
Hi Nick,
The reason for starting the setup again, is the following.
If an user buys another module he wants to install this module. And therefore he needs to start the setup again and enter the new serial number with the new module in it.
The serial check will be done between the serial dialog (where the user has do enter the serial number) and the custom setup dialog. Both (checking serial and changing dialog to custom setup) are triggered by the "Next" Button.
And the Problem then is that this new module is not selected.
No I didn't look at the log file, because I'm not sure where this can be found!?
regards,
Mike
The reason for starting the setup again, is the following.
If an user buys another module he wants to install this module. And therefore he needs to start the setup again and enter the new serial number with the new module in it.
The serial check will be done between the serial dialog (where the user has do enter the serial number) and the custom setup dialog. Both (checking serial and changing dialog to custom setup) are triggered by the "Next" Button.
And the Problem then is that this new module is not selected.
No I didn't look at the log file, because I'm not sure where this can be found!?
regards,
Mike
Posted by:
aogilmor
17 years ago
If an user buys another module he wants to install this module. And therefore he needs to start the setup again and enter the new serial number with the new module in it.
The serial check will be done between the serial dialog (where the user has do enter the serial number) and the custom setup dialog. Both (checking serial and changing dialog to custom setup) are triggered by the "Next" Button.
And the Problem then is that this new module is not selected.
No I didn't look at the log file, because I'm not sure where this can be found!?
log file can be found in /l*v <path to log file of your choice>
as far as what you are trying to do, have a look at the Microsoft office MSI and see how they do it. It sounds like you are trying to add another feature (or app or Module, as you call it) to an existing product. This is what Office does. When you say "this new module is not selected" do you mean that it's not selected by default in a dialog box, not installed, what? You'll have to present the user with a dialog to add the feature (app, module, whatever) if you're re-running the setup.
Also, have a look at documentation on product codes, upgrade codes, etc. That might help.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.