I'm building an installer for an MVC web app using WiX. WiX is very poerwful but like most open source software, it is poorly documented and I have found myself relying on posts om newsnet which have , more often than not, led me down the garden path.
A couple of things which somebody may be able to cooberate.
1) Harvesting usinfg heat.exe - Because the installer project is incorporated into the TFS build process, I need to harvest 3rd party dlls from a common location. The build machine won't have the bin folder that I have when building locally so I have chosen to harvest my files from the nuget packages folder. The problem here is that it harvests absolutely every file in this folder and all its subfolders when I only really want a subset of this.
Even so, this subset consists of about 70 files or so so I don't want to be doing this manually. There is a command line switch that allows you to specify the type of output but it doesn't actually do anything. I've come to the conclusion that heat.exe doesn't do what it says on the tin but these issues will be addressed in the illusive version 4 release of the WiX toolset.
2) IIS extensions - The only IIS support appears to be for IIS6 though I've reached this conclusion from reading some rather old posts. However, there seems to be no mention anywhere of support for IIS7 so I'm assming that there are no IIS extensions for IIS7.
A couple of things which somebody may be able to cooberate.
1) Harvesting usinfg heat.exe - Because the installer project is incorporated into the TFS build process, I need to harvest 3rd party dlls from a common location. The build machine won't have the bin folder that I have when building locally so I have chosen to harvest my files from the nuget packages folder. The problem here is that it harvests absolutely every file in this folder and all its subfolders when I only really want a subset of this.
Even so, this subset consists of about 70 files or so so I don't want to be doing this manually. There is a command line switch that allows you to specify the type of output but it doesn't actually do anything. I've come to the conclusion that heat.exe doesn't do what it says on the tin but these issues will be addressed in the illusive version 4 release of the WiX toolset.
2) IIS extensions - The only IIS support appears to be for IIS6 though I've reached this conclusion from reading some rather old posts. However, there seems to be no mention anywhere of support for IIS7 so I'm assming that there are no IIS extensions for IIS7.
Comment