WIX Installer UI Is Not Identical - wix

I have wix bootstrapper & setup projects to make installer of add-in.
Setup project gives me .msi file & Bootstrapper gives me .exe file.
But when I am trying to install from both files, UI of installation dialog are showing totally different.
UI provided by bootstrapper (.exe file) :
UI provided by setup (.msi file) :
In setup project, I have used <UIRef Id="WixUI_Minimal" />.
How to make dialog UI of .msi as same as .exe

Related

Embed MSI into setup.exe with WiX

I have a wix installer. It creates a setup msi and exe. The exe will install the prerequisites required before installing the application.
The msi of course just installs the application.
I have users that keep clicking the msi and when they run the app for the first time is will crash because some things were not installed.
How can I combine the msi with the exe in the wix script so my users will only see the setup.exe and not have the chance to click on the msi?

Using Windows SDK Bootstrapper Packages with WiX

In tracking down another issue I came across the folder C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\Packages that looks like it contains a number of pre-made installer items for various programs. I have a project I am on now that requires Crystal Reports and would like to know:
1) Can I use the "Crystal Reports for .NET Framework 4.0" installer project found in this directory to install Crystal Reports using a WiX bootstrapper (exe output) or WiX project (msi output)?
2) How would I go about including this Crystal Reports installation package in the bootstrapper or msi project?
1) You can use pretty much any msi/exe setup into bootstrapper
2) If you want to include EXE/MSI into bootstrapper then have a look at the documentation http://wixtoolset.org/documentation/manual/v3/xsd/wix/packagegroup.html and i believe what you need is MsiPackage Element for .msi or if it's exe setup then you use ExePackage Element.

Generating .wxs file via MSDeploy package issue and WiX installer

I have an ASP.NET application and a Wix installer for it.In Wix project I referenced to web project.
I need to create .wxs file which contains web application files from Deploy Package.
I followed this steps http://www.paraesthesia.com/archive/2010/07/30/how-to-consume-msdeploy-staged-web-site-output-in-a.aspx , but it doesn't works for me.
The package successfully created, but .wxs file doesn't.
Make sure the .wxs files are included in the wix project.
I usually create empty files and include them in the wix project then the harvest tool overwrites them.

Using bootstrapper with MSI ui

I have MSI file that is ready to install. It contains a customized UI that also collects data from user. As part of installation, i would like to install following things if missing
.Net framework 4.0
Microsoft Visual C++ 2010 Redistributable Package (x64)
From what I learned, bootstrapper should contain UI as well. How can I use bootstrapper for only initiating prerequisites stage and then proceed with MSI UI installation?
If you use the Visual Studio Setup and Deployment projects bootstrapper (GenerateBootstrapper related things) then it will show your MSI UI after installing the prerequisites. It's a pretty simple bootstrapper.
I believe the custom bootstrapper UI you are thinking about is the new Burn functionality in WiX v3.6+. Burn is a lot more powerful and can create single, seamless user experience for multiple chained packages (.exe's or .msi's or .msp's or .msu's). Using Burn you can create a very custom UI that does not show any UI from your chained packages. Alternatively, you can have Burn show the MSI UI. Basically, Burn is highly configurable but does require a bit of extra work (since WiX toolset doesn't provide everything out of the box, yet).
To show the MSI UI when running in a Burn-based Bundle you'll need to add DisplayInternalUI='yes' to the MsiPackage elements you want to display. For example:
<Chain>
...
<MsiPackage ... DisplayInternalUI='yes' />
</Chain>
If you are using the wixstdba (which is very common), it will show it's UI until it comes time to install the .msi package. Then the .msi package UI will pop-up on top and return back to the wixstdba UI to complete the Bundle install. You could provide your own Bootstrapper Application if you want to change the way that the Bundle based UI shows up.

Distribute WPF app with WIX and .net Framework

I need to distribute my WPF application. I am using WIX for building the Setup.exe.
But I also need to ensure that the .net framework 4.0 is first installed on the user's PC. I have downloaded dotNetFx40_Full_x86_x64.exe but how do I create a WIX installation that will contain MyApp.Msi and the .net framework redistribution file?
What I really want is to have just 1 Setup.exe that contains and runs both installs(my.msi and the .exe) in order.
Can this be done with WIX? Is there a better solution?
You can use the WiX bootstrapper technology (referred to as Burn) to create a single bootstrapper to install .NET and your .msi. Burn will enable you to embed the .NET redistributable and your .msi into a single setup.exe as well.
A setup bootstrapper is the file that could install the .NET framework. You can read about the WiX bootstrapper here. If you want the final output to be one .EXE file, you can pack the bootstrapper and the .MSI file into a new .EXE file using IExpress. IExpress is included in your Windows installation.
With WiX + IExpress you can create an installation package contained in one .EXE file.