Click here to Skip to main content
15,881,967 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hi, to make it brief, I added into Visual Studio 2022 Windows Installer, it is supposed to be .MSI Setup project.

I added all the files and folders as well as logo into the project.

In settings, I changed directory name and desktop link and program link and etc...

So, in settings, there is an option x86 and x64 project. I would want to run the installer on both 32-bit and 64-bit target machine, as far as I know x86 option should work for both, or maybe I am wrong,

or I have to build both instances? For Intel, AMD, etc.???

So, my project 2.3 Gb, so I could not build as compressed setup option, since
it allows only 2 Gb MAX, so I tried compressed CABINET file.CAB file as an option, but failed as well error something like file "_02AUI67IO..." (some letters and numbers) cannot be installed because the file cannot be found in SETUP.CAB ,

but third option worked "as loose uncompressed files".

Is there a way to be able to compress into SETUP.MSI file or at least a .CAB
file on the side to be able to run the installer. Is there a way to have .EXE SETUP option in the project?

Those technical questions above I would like to have some of your opinion or suggestions.

Get back, thanks in advance.

What I have tried:

I tried several options in the project.
Posted
Updated 7-Dec-23 22:28pm
v3

Quote:
I would want to run the installer on both 32-bit and 64-bit target machine, as far as I know x86 option should work for both, or maybe I am wrong,

The 32-bit installer will install on both 32 and 64-bit Windows, but on 64-bit Windows, it'll install as a 32-bit app.

You cannot combine installer so it installs as 32-bit on 32-bit Windows and 64-bit on 64-bit Windows. You have to create separate .MSI's, one for 32-bit and one for 64-bit if you want your application to run as 64-bit on 64-bit Windows.

CAB files can be a maximum of 2GB, each, so you'll have to have multiple CAB's.

Really, for such a huge application, I wouldn't recommend using the built-in Installer project. I would go with a professional tool, like Wix, AvancedInstaller, InnoSetup, or InstallShield. You will have far greater control over building the installer.
 
Share this answer
 
Comments
Maciej Los 8-Dec-23 5:13am    
5ed!
It is not recommended to embed over 2 GB data in a single installer file. I'd suggest using technique known as a bootstrapping.
As you probably know, while installing Visual Studio, you get a small version of installer (network installer) which downloads the necessary files to the installation folder and then invokes "normal" installer (from installation folder). This "normal" installer uses files from the instlalation folder, then cleans that folder.

This is how the installer should work. As Dave mentioned, it's recommended to use separate installer for each system (32/64 bit).
 
Share this answer
 
Comments
Gennady46 8-Dec-23 11:19am    
Give me some time I will try several options you have mentioned, I will write back, thanks so much for your help!
Andre Oosthuizen 8-Dec-23 15:09pm    
My 5
Maciej Los 11-Dec-23 16:50pm    
Thank you, Andre.
Gennady46 11-Dec-23 17:51pm    
I found a great software "Paquet Builder", which is a much cheaper than others, it compresses files and makes executable even from MSI file. Thank you.
Maciej Los 12-Dec-23 13:39pm    
Good to know :)

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900