heat

Wix\heat.exe strange output

浪子不回头ぞ 提交于 2019-12-10 17:37:26
问题 I have a directory with one file there: Iesi.Collections.dll. When I run the following command: heat.exe dir D:\MyDir -cg References -srd -o D:\Product.wxs -nologo -gg -g1 -dr INSTALLFOLDER I got really strange output. May be it is strange only for me so please explain it to me. Why I get these registry values? I get the same result for any third party dll like MassTransit or RabbitMQ. Expected output: <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi

Wix heat for per machine installer

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-10 10:03:09
问题 I use the following command to create a wxs file for class registry, using heat : "C:\Program Files\Windows Installer XML v3.5\bin\heat.exe" file MyAddin.dll -ag -template fragment -out MyAddin.wxs The result is registry entries per user. In the following lines from the created wxs file you can see HKCU -- for HKEY_CURRENT_USER : <Class Id="{1AF5E2B9-CC02-368F-A879-1DF3F538D71A}" Context="InprocServer32" Description="AdminAddins.MyClass" ThreadingModel="both" ForeignServer="mscoree.dll">

Harvesting a .csproj with heat.exe in Visual Studio 2008 and WiX(v3)

帅比萌擦擦* 提交于 2019-12-10 03:41:43
问题 I found that Wix v3 uses a tool (heat.exe) to "harvest" information into WiX fragments. Either I am looking in the wrong location, or this is thinly documented. What is the best way to auto-generate a WiX fragment (likely using heat.exe) for a complex folder structure that contains media files: Of varying types (ico/png/xaml/etc) That may change regularly (names/locations/adds/removes) That are classified as "Content" and included in a .csproj such that they can be built into an installer via

Wix Heat - Replace an autogenerated GUID with known string using XSLT

元气小坏坏 提交于 2019-12-08 03:57:52
问题 I'm working on migrating a Windows Service VDPROJ to WiX. I was able to use HEAT to harvest output from my Windows Service project into a fragment. Currently, in order for my custom actions to work properly, I manually change some of the generated GUIDs from the Heat-generated file into known strings that are referenced in the main Product.wxs. I need to do this programmatically on every build instead of relying on manual intervention since I need to integrate the WiX project into our

Wix Harvest: Same Component/File ID when files are in different folders

我们两清 提交于 2019-12-08 00:37:12
问题 So I may not be doing this correct, but here it goes: I have one application with references to 4 SQL Server assemblies App must work against SQL 2008 and 2010. The only way I've gotten this to work is, to have my app reference a 'generic' path for my SQL Assemblies. Then in my MSBuild project, I copy the 2008 assemblies to the 'generic' folder and compile my app. I do this again for the 2012. I have a folder like Tools\Release\V2008 and Tools\Release\V2010. These folders have all the EXE and

gnuplot heat map color range

て烟熏妆下的殇ゞ 提交于 2019-12-07 00:33:42
问题 I have some X Y Z data in a file and I'm using gnuplot to display it. I am creating a heat map, ie. a 2D plot where the Z value is presented using color. Right now I'm using the following script: set palette defined (0 "blue", 1 "red") plot "xyz.dat" u $1:$2:$3 w image My problem is, gnuplot ignores the 0 and 1 in the palette definition. It uses the colors specified, but rescales according to the minimal and maximal Z value in the file. This makes it hard to visually compare different plots

Wix Heat - Replace an autogenerated GUID with known string using XSLT

南楼画角 提交于 2019-12-06 15:22:44
I'm working on migrating a Windows Service VDPROJ to WiX. I was able to use HEAT to harvest output from my Windows Service project into a fragment. Currently, in order for my custom actions to work properly, I manually change some of the generated GUIDs from the Heat-generated file into known strings that are referenced in the main Product.wxs. I need to do this programmatically on every build instead of relying on manual intervention since I need to integrate the WiX project into our continuous build server. From what I could research, I can use an XSLT transform on the output of HEAT to

Wix Harvest: Same Component/File ID when files are in different folders

自闭症网瘾萝莉.ら 提交于 2019-12-06 05:53:39
So I may not be doing this correct, but here it goes: I have one application with references to 4 SQL Server assemblies App must work against SQL 2008 and 2010. The only way I've gotten this to work is, to have my app reference a 'generic' path for my SQL Assemblies. Then in my MSBuild project, I copy the 2008 assemblies to the 'generic' folder and compile my app. I do this again for the 2012. I have a folder like Tools\Release\V2008 and Tools\Release\V2010. These folders have all the EXE and required DLLs (including the 4 sql server). I run HEAT against these folders. However, when I run heat

How to create shortcuts to files harvested by heat.exe?

旧城冷巷雨未停 提交于 2019-12-05 22:24:29
Using WiX Toolset 3.10, and trying to create shortcuts to certain files that have been harvested with the heat.exe utility, as by: "%WIX%\bin\heat.exe" dir SourceDir -nologo -platform x64 ^ -ke -gg -g1 -suid -srd -scom -sreg -dr INSTALLDIR ^ -cg ProjFiles -out ProjFiles.wxs My issues: I know by now that I'm supposed to use an XSLT file to transform ProjFiles.wxs (the -t option in heat.exe ) but WiX-specific documentation on how to write it is non-existent: can someone please provide an example that adds a Shortcut on the Desktop for an Id of "Prog.exe"? Because of the -g1 flag, files which

Wix heat for per machine installer

时间秒杀一切 提交于 2019-12-05 19:33:46
I use the following command to create a wxs file for class registry, using heat : "C:\Program Files\Windows Installer XML v3.5\bin\heat.exe" file MyAddin.dll -ag -template fragment -out MyAddin.wxs The result is registry entries per user. In the following lines from the created wxs file you can see HKCU -- for HKEY_CURRENT_USER : <Class Id="{1AF5E2B9-CC02-368F-A879-1DF3F538D71A}" Context="InprocServer32" Description="AdminAddins.MyClass" ThreadingModel="both" ForeignServer="mscoree.dll"> <ProgId Id="AdminAddins.MyClass" Description="AdminAddins.MyClass" /> </Class> <File Id=