self-extracting

I'm interested in knowing how WiX is bundling the EXE files created with Burn. I know that creating a self-extracting EXE file is pretty straightforward, having done it a million times in WinRAR . What directory is the EXE file being unpacked to, and how is the installation writing that location into Add/Remove Programs? Also, how is the UX file being kept around for the uninstall? And even more interesting, what goes on during an upgrade? Burn doesn't create a typical "self-extracting .exe" that unpacks the contents then launches. Instead, it extracts the bits it needs (the UX or bootstrapper

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. I've seen executables that extract themselves and run a compressed setup.exe afterwards: a double click on the file uncompresses it and then runs the formerly compressed setup.exe . How can I accomplish this? I would like to use WinRAR, how can I make a self-extracting executable that runs the compressed setup.exe after unpacking it to a temporary folder? New Archive, set to SFX mode. Go to Advanced tab, SFX Options

According to the answers to this question, I cannot embed a file version in my .msi file. The installer that I give the client needs to have a file version. So, what I want to do is create a self-extracting executable containing the msi file and the setup.exe generated by Visual Studio, and put the file version on this self-extracting executable instead. Therefore, I need a utility to create self-extracting executables which supports embedding a file version in its output. It also needs to support automatically running a file after extraction, so I can start the real installer automatically.

If this is not the correct place to ask this, I apologize. I use 7zip to create an installer package. Recently, my computer was updated, and I can no longer get it to work. I use a Windows Installer from Visual Studio 2010 to create the installation package, which I add to a file called setup.7z. I have confirmed that the files are archived correctly. I then call copy /b 7zsd.sfx + config.txt + setup.7z setup.exe which packages everything into a single file called " setup.exe ". Clicking on this would start the installer. After the update, I can still make the file, and it looks just fine.