Installation through .msi & .exe

Got a problem you cannot solve? Try here.
SITL
Posts: 116
Joined: Tue Sep 27, 2016 12:31 am

Installation through .msi & .exe

Postby SITL » Tue Jul 04, 2017 5:29 am

Dear Francesco,

Thanks for all the help.
Both Base project and Patch are working as expected. (with few minor issues )
-------------------------------------------------------------------------------------------
I got this bug our from QA team.
This is regarding Base installer (NO PATCH).
IT's our process, we ship both MyProduct.msi & MyProduct.exe files for installation.
Here is what happened ...
1. Installed MyProduct thro' Silent install using MyProduct.msi file.

2. Accedentally, the person has double clicked on MyProduct.exe (Other installer).
a. Installation started showing the UI & finally installed successfully.
( it was supposed to bring up Maintenance dialog).
b. previous installation of MyProduct was automatically uninstalled, without asking us to confirm.

QUESTIONS
1. Is this expected ? Need you comments
2. How to check whether the Drive exists ?
Example - E:\XYZ path for silent install.
"E Drive" does not does not exists.
Please share your comments.

Regards
SITL

FrancescoT
Site Admin
Posts: 5360
Joined: Sun Aug 22, 2010 4:28 am

Re: Installation through .msi & .exe

Postby FrancescoT » Tue Jul 04, 2017 11:01 am

Dear SITL,

1. Yes, this the expected behavior and it depends on the value of the "REVISIONCODE" (Pre-Defined Variable) defined with the project.

REVISIONCODE, The Revision Code must be unique for each different setup. Unless each setup you build has a unique code, they will appear to be the same installation package to Windows Installer, even when they are not. Even slightly different versions of your setup must have a unique revision code. By default InstallAware automatically update this code every time you build your setup project.
https://www.installaware.com/forums/viewtopic.php?f=2&t=10734

2. You may call (via "Call DLL Function") the "GetLogicalDriveStrings" or "GetLogicalDrives" (WINAPI) at such purpose.
For more details;
https://msdn.microsoft.com/en-us/library/windows/desktop/aa364975(v=vs.85).aspx

Regards
Francesco Toscano
InstallAware Software

White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE

SITL
Posts: 116
Joined: Tue Sep 27, 2016 12:31 am

Re: Installation through .msi & .exe

Postby SITL » Wed Jul 05, 2017 2:03 am

Dear Francesco,

Thank you very much for sharing your knowledge.
For checking whether the given Drive is valid or not, I have some work around & i'll post it under appropriate topic.

Regards
SITL

SITL
Posts: 116
Joined: Tue Sep 27, 2016 12:31 am

Re: Installation through .msi & .exe

Postby SITL » Thu Jul 06, 2017 6:18 am

Dear Francesco,
Thanks for your all the help.
Few questions,
1. when my BASE build is MyProduct.msi & patch reference MyProduct.msi
I'm not able to build patch, Is this allowed ?.

2. It's our process, we have very old customers who are using
silent install ... (msiexec /i myproduct.msi etc., )
So we ship both MyProduct.exe & MyProduct.msi (.msi is compulsary )



NOTE : my thoughts...
a. Note down REVISION CODE before the build
b. build base project MyProduct.exe
c. Enter the same REVISION CODE &
d. Build BASE Project as .msi
f. finally build patch with patch reference as .exe
(because patch reference as .msi is not building )

Result: a. For those who installed through MyProduct.exe , patch is applied properly.
b. For those who installed MyProduct through MyProduct.msi, are not
able to apply patch, it is not able to locate sources.

How to create a patch which will work for both the users ? (.msi & .exe )
Please Suggest some solution.
Thanks.
Regards
SITL

FrancescoT
Site Admin
Posts: 5360
Joined: Sun Aug 22, 2010 4:28 am

Re: Installation through .msi & .exe

Postby FrancescoT » Fri Jul 07, 2017 5:00 am

Dear SITL,

it will not work with entering the REVISIONCODE manually.

To build the respective MSI/EXE installers, you need need to keep disabled the flag; "Change revision code automatically upon rebuild" in the project option dialog. > SHIFT+CTRL+F11 -> Build Node -> Output Node <

Then, don't forget to re-enable the flag once done.

Hope this helps you.

Regards
Francesco Toscano
InstallAware Software

White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE


Return to “Technical Support”

Who is online

Users browsing this forum: Google [Bot] and 45 guests