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.
Related
How to set the service version as the installer version, using wix?
How to set it by the installer's coding, NOT by GUI.
For example : running service creates a .exe file in the bin folder.
Versioning your application files should happen before building your installer. WiX just copies files to the destination and doesn't modify them in anyway. (That would break code signing if it did.)
I have a .vdproj setup project, unfortunately, and it references some Wix projects.
Unfortunately the reference can only really be a File (full path) as the Project Output reference only permits .dll and .exe, the Wix ouput is .msi.
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.
I have a Wix 3.6 managed bootstrapper in which the user can select individual packages to download and install. I want to show the download size of each package. How can I access the file size of each packages in the Bundle?
I guess this information is available somewhere in the Wix framework (because the file hashes are used to validate the downloaded files), but I did not find it.
I have an idea for a workaround, but it would be more implementation for me:
Have a wxs file generated programmatically that contains Variable elements containing the file size of the packages. Those variables would be read by the bootstrapper.
When your bundle is created, a BootstrapperApplicationData.xml is added to the bundle. That XML file contains a lot of metadata about the bundle and contained packages. Your bootstrapper application code can load this file by looking in the same direcotry as your bootstrapper application dll lives.
I did not found how by using the burn API, but I implemented my own workaround:
If the local file is present
query the file system
else
query the web server
I'm new to WIX installer and would appreciate if someone could help me solve the below issue.We have a web application where we load plugin assembly(non referenced) using reflection and a web deployment project which merges all the assemblies in to a single one. In the webdeployment project file there are couple of lines which generates the "ProjectWebFiles.wix" source file when built.
<PropertyGroup>
...........
<WixDirectoryId>ProjectWebFolder</WixDirectoryId>
<WixComponentGroupId>ProjectWebFiles</WixComponentGroupId>
</PropertyGroup>
We have a WIX installer project which creates msi installer from this wix file and we want the web application project bin folder to have the unreferenced assembly when the application is installed using msi.
One solution is we could add the project as a static reference to the web project but we want to keep that as a last option since we have to build the web project everytime the plugin project is modified.
Can this be achieved by modifying the web application deployment project file ?
That is MSBuild syntax, not WiX syntax, so I'm not exactly sure what you are asking for. If you are just trying to get all the files from another project or directory, then take a look at the HeatProject task and/or HeatDirectory task.