This is a bit of a longshot but there may be a way.
I'm investigating creating msi installations for some software we have that doesn't already have an msi file.
The aim is to have silent installs for all of the programs we have.
I was wondering if instead of creating an msi file why can't I just create a program that waits for prompts to appear and auto fills them or hits ok or whatever.
I guess the hardest parts would be to identify what action to do and when from the forms that appear during the setup process. If these had something unique that I can read and then react to I could possibly do this.
The other stummbling block would be performing the action on the other program(the installation package). Could this be as simple as getting the location of the active form and knowing the form layout "simulating" a mouse click on the relevant part of the screen (eg a button)?
Not sure if any of this is do-able.
Some advice on this would be great.
Cheers,
I'm investigating creating msi installations for some software we have that doesn't already have an msi file.
The aim is to have silent installs for all of the programs we have.
I was wondering if instead of creating an msi file why can't I just create a program that waits for prompts to appear and auto fills them or hits ok or whatever.
I guess the hardest parts would be to identify what action to do and when from the forms that appear during the setup process. If these had something unique that I can read and then react to I could possibly do this.
The other stummbling block would be performing the action on the other program(the installation package). Could this be as simple as getting the location of the active form and knowing the form layout "simulating" a mouse click on the relevant part of the screen (eg a button)?
Not sure if any of this is do-able.
Some advice on this would be great.
Cheers,