visual-studio,wix,windows-installer,installer,heat
I suppose you could use external source files if that's acceptable - then you don't have a lengthy compression operation taking place during the build, just a file copy (which keeps getting faster - especially with flash drives). With techniques for making yourself a debug build, you can save a...
You can edit the output generated by Heat using XSL. That way you can transform the ID fil023E197261ED7268770DDE64994C4A55 into something more readable which can be referenced in your project. To apply a transform to a HeatDirectory task you have to specify its Transforms attribute and set its value to a...
The heat command cannot be a pre build event. I kind of had a feeling that Jenkins is not waiting for my C# project to be built but I don't 100% know what it's doing exactly. I changed heat to run at AfterResolveReferences which is still a pre build event...
It's depends on computer configuration. Most modern hardware has overheat protection, they just shutdown on throttle performance or otherheat. But be careful, you can just loose your calculations because of this.
Usually, path environments (%windir%, %temp%, etc) uses backslashes (\). try modifying your arguments to use backslashes instead of slashes (\"%WIX% \ bin \ heat.exe\"...