<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Heat Archives - scmGalaxy</title>
	<atom:link href="https://www.scmgalaxy.com/tutorials/tag/heat/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scmgalaxy.com/tutorials/tag/heat/</link>
	<description>A Platform for Software Engineers</description>
	<lastBuildDate>Sat, 21 Feb 2026 07:13:05 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>
	<item>
		<title>Top 21 Tools for Heat Mapping Tools in 2026</title>
		<link>https://www.scmgalaxy.com/tutorials/top-21-tools-for-heat-mapping-tools-in-2025/</link>
					<comments>https://www.scmgalaxy.com/tutorials/top-21-tools-for-heat-mapping-tools-in-2025/#respond</comments>
		
		<dc:creator><![CDATA[Vijay K]]></dc:creator>
		<pubDate>Thu, 13 Feb 2025 10:22:25 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[2025]]></category>
		<category><![CDATA[21]]></category>
		<category><![CDATA[Heat]]></category>
		<category><![CDATA[Mapping]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Top]]></category>
		<guid isPermaLink="false">https://www.scmgalaxy.com/tutorials/?p=11932</guid>

					<description><![CDATA[<p>1. Hotjar Hotjar is a popular heat mapping tool that provides insights into user behavior on websites through features like [&#8230;]</p>
<p>The post <a href="https://www.scmgalaxy.com/tutorials/top-21-tools-for-heat-mapping-tools-in-2025/">Top 21 Tools for Heat Mapping Tools in 2026</a> appeared first on <a href="https://www.scmgalaxy.com/tutorials">scmGalaxy</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" width="1024" height="575" src="https://www.scmgalaxy.com/tutorials/wp-content/uploads/2025/02/image-33-1024x575.png" alt="" class="wp-image-11933" srcset="https://www.scmgalaxy.com/tutorials/wp-content/uploads/2025/02/image-33-1024x575.png 1024w, https://www.scmgalaxy.com/tutorials/wp-content/uploads/2025/02/image-33-300x168.png 300w, https://www.scmgalaxy.com/tutorials/wp-content/uploads/2025/02/image-33-768x431.png 768w, https://www.scmgalaxy.com/tutorials/wp-content/uploads/2025/02/image-33.png 1225w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">1. Hotjar</h1>



<p class="wp-block-paragraph">Hotjar is a popular heat mapping tool that provides insights into user behavior on websites through features like heat maps, session recordings, and surveys. Its heatmaps visually represent where users click, scroll, and hover on a page. Hotjar&#8217;s user-friendly interface allows teams to quickly identify areas of interest or friction, helping optimize user experience and conversions.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">2. Crazy Egg</h1>



<p class="wp-block-paragraph">Crazy Egg offers a suite of heat mapping tools, including click maps, scroll maps, and user recordings. It helps businesses understand how users interact with their website by providing visual data on clicks, movements, and scroll depth. Crazy Egg’s A/B testing and visual editor make it easy for teams to make data-driven design changes and enhance user engagement.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">3. Lucky Orange</h1>



<p class="wp-block-paragraph">Lucky Orange is a website optimization tool that includes heat mapping features along with session replays, form analytics, and visitor recordings. It helps businesses understand user behavior by visualizing clicks, scrolls, and movements on a page. Lucky Orange also offers real-time chat support, enabling instant interaction with users to resolve issues quickly.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">4. Mouseflow</h1>



<p class="wp-block-paragraph">Mouseflow provides a comprehensive suite of heat mapping tools, including click maps, scroll maps, attention maps, and more. It allows teams to analyze user behavior on websites, track engagement, and identify usability issues. Mouseflow also includes session replay, which helps teams watch user interactions and understand how they navigate through a site.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">5. SessionCam</h1>



<p class="wp-block-paragraph">SessionCam provides heat mapping and session replay features to help teams visualize user interactions on their websites. It tracks user clicks, scrolls, and mouse movements to provide actionable insights into the user experience. SessionCam’s unique focus on session recording and journey mapping allows businesses to optimize customer experiences and increase conversion rates.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">6. Visual Website Optimizer (VWO)</h1>



<p class="wp-block-paragraph">VWO is a comprehensive website optimization tool that includes heat maps, A/B testing, and user feedback collection. VWO provides various heat map types, such as click maps, scroll maps, and mouse tracking, to help businesses understand user behavior. Its intuitive dashboard and deep analytics allow for quick analysis and optimization of website performance.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">7. Inspectlet</h1>



<p class="wp-block-paragraph">Inspectlet is a tool that combines heat mapping, session recording, and form analytics to provide valuable insights into user behavior. It includes click, scroll, and movement heat maps, along with session replays to see how users interact with your website. Inspectlet helps identify usability issues, optimize design, and enhance user experience.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">8. FullStory</h1>



<p class="wp-block-paragraph">FullStory offers a robust heat mapping tool with session replay, click tracking, and user interaction analysis. It provides in-depth visual analytics and segmentation features to help businesses better understand user journeys. FullStory’s powerful search and filtering options allow teams to quickly pinpoint issues and improve website performance.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">9. Plerdy</h1>



<p class="wp-block-paragraph">Plerdy is a comprehensive conversion optimization tool that includes heat mapping, session recording, and SEO audit features. It allows teams to track user clicks, scroll depth, and mouse movements with its visual heat maps. Plerdy also offers an easy-to-use dashboard for tracking and analyzing user interactions, providing insights to enhance website engagement and conversion rates.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">10. ClickTale</h1>



<p class="wp-block-paragraph">ClickTale (now a part of Contentsquare) offers advanced heat mapping tools that visualize clicks, mouse movements, and scroll activity. It helps businesses understand the user journey through session replays and detailed behavioral analytics. ClickTale’s in-depth reporting capabilities help teams identify key areas for improvement in user experience and site design.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">11. Heatmap.me</h1>



<p class="wp-block-paragraph">Heatmap.me is a simple and user-friendly heat mapping tool that provides click and scroll heat maps to analyze user interactions. It offers real-time heat map tracking, allowing businesses to see how users engage with various parts of a website. Heatmap.me is a great option for small businesses or teams looking for a straightforward tool to optimize website performance.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">12. Yandex Metrica</h1>



<p class="wp-block-paragraph">Yandex Metrica is a free web analytics tool that includes heat mapping features such as click maps, scroll maps, and user session recordings. It provides detailed insights into user behavior, enabling businesses to track how users navigate through websites. Yandex Metrica also includes tools for goal tracking and funnel analysis, making it a comprehensive analytics solution.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">13. Smartlook</h1>



<p class="wp-block-paragraph">Smartlook offers heat maps, session replays, and event tracking to help businesses analyze user behavior and optimize websites. Its heat maps track clicks, movements, and scroll depth, while session replays provide visual insights into how users interact with the site. Smartlook also provides event tracking to measure specific user actions, helping teams refine the user experience.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">14. ClickHeat</h1>



<p class="wp-block-paragraph">ClickHeat is a simple, open-source heat mapping tool that tracks click data and visualizes it on web pages. It helps businesses understand which areas of a page attract the most attention from users. ClickHeat offers customizable settings, allowing teams to tailor the heat maps to specific goals and track user behavior on both desktop and mobile devices.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">15. Crazy Egg (Formerly Kissmetrics)</h1>



<p class="wp-block-paragraph">Crazy Egg offers heat maps, scroll maps, and A/B testing tools to help businesses analyze user behavior and optimize website performance. It provides insights into how users interact with different page elements and tracks engagement metrics. The tool’s intuitive dashboard and detailed reports allow businesses to identify areas of improvement and refine user experience effectively.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">16. Zoho PageSense</h1>



<p class="wp-block-paragraph">Zoho PageSense is an A/B testing and website optimization tool that includes heat maps, session recording, and visitor analytics. It provides click maps, scroll maps, and attention maps to help businesses track user interactions and optimize conversions. Zoho PageSense also integrates with Google Analytics and other marketing tools for enhanced tracking and reporting.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">17. Convert Experiences</h1>



<p class="wp-block-paragraph">Convert Experiences is an A/B testing and conversion optimization tool that includes heat mapping capabilities. It allows users to track clicks, scroll behavior, and mouse movements on websites. Convert Experiences also offers multivariate testing, session recording, and user feedback collection, providing a full suite of tools to enhance website performance.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">18. Mouse Tracking by Crazy Egg</h1>



<p class="wp-block-paragraph">Crazy Egg’s mouse tracking feature is designed to track where users move their mouse on the page, offering valuable insights into how users engage with website content. It also provides additional heat map types, such as click and scroll maps, to enhance the analysis of user behavior. This feature is useful for understanding the areas of a page that attract the most attention.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">19. Smartlook Heatmap</h1>



<p class="wp-block-paragraph">Smartlook Heatmap is a feature of the Smartlook platform that tracks user behavior, including clicks, scrolls, and mouse movements. It provides easy-to-understand visual heat maps that help teams analyze user interactions and optimize website design. The tool also includes session recording, funnel tracking, and event tracking to enhance the understanding of user experience.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">20. Lucky Orange</h1>



<p class="wp-block-paragraph">Lucky Orange offers a comprehensive set of heat mapping tools, including click maps, move maps, and scroll maps. It also includes session replay, form analytics, and live chat features to help teams engage with users and understand their behavior. Lucky Orange provides powerful insights into user actions, helping businesses make data-driven decisions to improve website conversions.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<h1 class="wp-block-heading">21. Clicky</h1>



<p class="wp-block-paragraph">Clicky is a website analytics tool that offers heat mapping and detailed visitor analytics. It tracks user clicks, scrolls, and engagement metrics, providing teams with real-time data on user behavior. Clicky’s heat maps and visitor tracking features allow businesses to identify trends and optimize content for higher engagement and conversion rates.</p>



<hr class="wp-block-separator has-alpha-channel-opacity">



<p class="wp-block-paragraph">This list provides a variety of heat mapping tools to help businesses optimize user experience, improve design, and increase conversion rates. Let me know if you would like any additional details or modifications!</p>
<p>The post <a href="https://www.scmgalaxy.com/tutorials/top-21-tools-for-heat-mapping-tools-in-2025/">Top 21 Tools for Heat Mapping Tools in 2026</a> appeared first on <a href="https://www.scmgalaxy.com/tutorials">scmGalaxy</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.scmgalaxy.com/tutorials/top-21-tools-for-heat-mapping-tools-in-2025/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Using Heat multiple times =&gt; Duplicate symbols</title>
		<link>https://www.scmgalaxy.com/tutorials/using-heat-multiple-times-duplicate-symbols/</link>
					<comments>https://www.scmgalaxy.com/tutorials/using-heat-multiple-times-duplicate-symbols/#respond</comments>
		
		<dc:creator><![CDATA[scmgalaxy K]]></dc:creator>
		<pubDate>Mon, 04 Dec 2017 05:54:58 +0000</pubDate>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Heat]]></category>
		<guid isPermaLink="false">http://www.scmgalaxy.com/tutorials/?p=1251</guid>

					<description><![CDATA[<p>InstallerGeek created the topic: Using Heat multiple times => Duplicate symbols Hello all, I am using heat to generate the [&#8230;]</p>
<p>The post <a href="https://www.scmgalaxy.com/tutorials/using-heat-multiple-times-duplicate-symbols/">Using Heat multiple times =&gt; Duplicate symbols</a> appeared first on <a href="https://www.scmgalaxy.com/tutorials">scmGalaxy</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>InstallerGeek created the topic: Using Heat multiple times => Duplicate symbols</strong><br />
Hello all,</p>
<p>I am using heat to generate the source for two .wixlibs which are lighted together with some other pieces to form my final MSI.  Heat is used on two different directories at build time.  One of these directories holds all of my language specific files &#8220;/localized/&#8221; and the other holds all of my language neutral files &#8220;/neutral/&#8221;.  Creating a setup this way allows me to generate the language neutral .wixlib just once for every locale I support.<br />
The problem is that the directory structure within those directories has some (but not complete) overlap.  e.g.</p>
<p>localized<br />
  foo<br />
    greeneggs<br />
  bar</p>
<p>neutral<br />
  foo<br />
    ham</p>
<p>becomes on the user&#8217;s computer<br />
installdir<br />
  foo<br />
    greeneggs<br />
    ham<br />
  bar</p>
<p>This gives me a duplicate symbol error at foo when I try to link the two wixlibs together.  I can&#8217;t just throw away the directory fragments from one heat run because neither structure is a subset of the other.  I also don&#8217;t want to tell light to suppress the duplicate symbols error (and I don&#8217;t know that that will produce a working MSI).  Really the only solution I&#8217;ve come up with is to use XSLT to eliminate all of the directory elements from the first two runs and then run heat again against the combined result and use XSLT on that third run to eliminate all of the non-directory elements.</p>
<p>That seems suboptimal at best.  Anyone have any better ideas?</p>
<p><strong>applicationPackaging replied the topic: Re: Using Heat multiple times => Duplicate symbols</strong><br />
Hi Kyle,</p>
<p>What about using the XSLT to change the duplicate <Directory/> elements to <DirectoryRef/> elements, and define the directory structure once, in another file?</p>
<p>I do something like this when I first create a setup project&#8211;I do not use HEAT dynamically at build time. I like to have the directory structure laid out in one place where it&#8217;s easier to visualize how it will look on the target system.</p>
<p><strong>applicationPackaging replied the topic: Re: Using Heat multiple times => Duplicate symbols</strong><br />
How about using XSLT to change the <Directory Id="foo" ...> into <DirectoryRef Id="foo"> in the localized wixlib&#8217;s wxs file from heat?</p>
<p><strong>InstallerGeek replied the topic: Re: Using Heat multiple times => Duplicate symbols</strong><br />
Yeah, this is more or less what I&#8217;m doing.  The issue is that I still need to define the directory structure somewhere.  Zach suggests defining it manually which is probably the best solution but unfortunately isn&#8217;t really an option for what I&#8217;m doing.  What would be ideal is if light would handle a duplicate symbol definition if the symbols are identical (same ID and attributes, etc.) by outputting the symbol once instead of choking.  Of course, there may be good reasons I haven&#8217;t thought of not to do that &#8211; I&#8217;m not sure.  I&#8217;m hoping that someone has solved the same problem in a manner that avoids this problem.</p>
<p><strong>applicationPackaging replied the topic: Re: Using Heat multiple times => Duplicate symbols</strong><br />
Looking at your situation, this is what looks to me to be your solution:</p>
<p>1- I&#8217;m assuming that your transformed heat outputs don&#8217;t have any Directory elements with an Id of either localized or neutral. Remove them if they exist in your transform.<br />
2- Under your Product element (or some other manually authored location that is linked into your final MSI):<br />
    <Directory Id='INSTALLDIR' ...><!--INSTALLDIR will likely live under other Directory element(s) as needed to create a correct directory tree--><br />
      <Directory Id='foo' .../><br />
      <Directory Id='bar' .../><br />
    </Directory><br />
3- In your transformed localized sources from heat:<br />
    <DirectoryRef Id='foo'><br />
      &#8230;<br />
      <Directory Id='greeneggs'><br />
        &#8230;<br />
      </Directory><br />
      &#8230;<br />
    </Directory><br />
    <DirectoryRef Id='bar'><br />
      &#8230;<br />
    </Directory></p>
<p>4- In your transformed neutral sources from heat:<br />
    <DirectoryRef Id='foo'><br />
      &#8230;<br />
      <Directory Id='ham'><br />
        &#8230;<br />
      </Directory><br />
      &#8230;<br />
    </Directory></p>
<p>So your transform will need to look at the directory tree that heat produces and transform that to get the above results (by altering at and above the level of the children of installdir and leaving the others unless you start creating some of them as well).</p>
<p>If you have files in installdir as well as the above subdirs you will need to also declare a DirectoryRef for that directory so that the fragment(s) from heat can be linked into your wixlibs. The only directories you have to transform/manually deal with are those that are in common. The above lets you simply harvest the unique directories as they are laid out without having to manually deal with them.</p>
<p><strong>InstallerGeek replied the topic: Re: Using Heat multiple times => Duplicate symbols</strong><br />
Hey Everyone,</p>
<p>Why can&#8217;t you heat the sub directories &#8220;greeneggs&#8221; and &#8220;ham&#8221; directly and use the -srd and -dr FOO switches? I do understand if there are additional sub directories this might be a bit more difficult. However, you could re-arrange your source directories to handle these issues if necessary, no?</p>
<p>The post <a href="https://www.scmgalaxy.com/tutorials/using-heat-multiple-times-duplicate-symbols/">Using Heat multiple times =&gt; Duplicate symbols</a> appeared first on <a href="https://www.scmgalaxy.com/tutorials">scmGalaxy</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.scmgalaxy.com/tutorials/using-heat-multiple-times-duplicate-symbols/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Heat.exe</title>
		<link>https://www.scmgalaxy.com/tutorials/heat-exe/</link>
					<comments>https://www.scmgalaxy.com/tutorials/heat-exe/#respond</comments>
		
		<dc:creator><![CDATA[scmgalaxy K]]></dc:creator>
		<pubDate>Mon, 04 Dec 2017 05:27:12 +0000</pubDate>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Heat]]></category>
		<guid isPermaLink="false">http://www.scmgalaxy.com/tutorials/?p=1224</guid>

					<description><![CDATA[<p>InstallerGeek created the topic: heat.exe Hi, I have some problems to migrate from WIX 3.0.4707 to WIX 3.0.5419 because the [&#8230;]</p>
<p>The post <a href="https://www.scmgalaxy.com/tutorials/heat-exe/">Heat.exe</a> appeared first on <a href="https://www.scmgalaxy.com/tutorials">scmGalaxy</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>InstallerGeek created the topic: heat.exe</strong><br />
Hi,<br />
I have some problems to migrate from WIX 3.0.4707 to WIX 3.0.5419 because the arguments of HEAT.EXE changed.<br />
usage:  heat.exe harvestType harvestSource <harvester arguments> -o[ut] sourceFile.wxs What is meant with the new argument harvestSource?<br />
The old command looks like this:<br />
&#8220;C:\Program Files\Windows Installer XML v3\bin\heat.exe&#8221; dir  &#8220;..\..\~tmp\j2build3v_win\apps&#8221; -gg -sfrag -scom -sreg &#8220;$(ProjectDir)..\..\..\~tmp\j2build3v_win\apps\eu&#8221; -out &#8220;$(ProjectDir)gen_fragment.wxs&#8221; -template:fragment How can I convert it to the new implemtation of HEAT?</p>
<p><strong>InstallerExpert replied the topic: Re: heat.exe</strong><br />
Hi,<br />
I have some problems to migrate from WIX 3.0.4707 to WIX 3.0.5419 because the arguments of HEAT.EXE changed.<br />
usage:  heat.exe harvestType harvestSource <harvester arguments> -o[ut] sourceFile.wxs What is meant with the new argument harvestSource?<br />
The old command looks like this:<br />
&#8220;C:\Program Files\Windows Installer XML v3\bin\heat.exe&#8221; dir  &#8220;..\..\~tmp\j2build3v_win\apps&#8221; -gg -sfrag -scom -sreg &#8220;$(ProjectDir)..\..\..\~tmp\j2build3v_win\apps\eu&#8221; -out &#8220;$(ProjectDir)gen_fragment.wxs&#8221; -template:fragment How can I convert it to the new implemtation of HEAT?</p>
<p><strong>InstallerExpert replied the topic: Re: heat.exe</strong><br />
I am in the midst of upgrading our product to be VS 2010 compatible. We&#8217;re using WIX to generate a .msi installer. I&#8217;ve upgraded to WIX 3.5.1309.0 and have run into a snag.</p>
<p>Specifically I&#8217;m having a problem with the HEAT tool in this version. It is having trouble working with our VS2010 converted .csproj files. Votive wants to automatically run this command line:</p>
<p>C:\Program Files\Windows Installer XML v3.5\bin\Heat.exe project &#8220;..\..\Common\ArtOfTest.Common.Design\ArtOfTest.Common.Design\ArtOfTest.Common.Design.csproj&#8221; -pog:Binaries -pog:Symbols -pog:Sources -pog:Content -pog:Satellites -pog:Documents -ag -sfrag -out obj\Release\_ArtOfTest.Common.Design.wxs</p>
<p>If I manually run this at the command line and point it to the working VS2008 .csproj file I get the expected output file just fine. But if I point it to the converted VS2010 .csproj file (which does compile and generates a .dll in VS2010 no problem), nothing gets output. There&#8217;s no error message of any kind either. I tried adding the -verbose switch and that didn&#8217;t add any output either. Absolutely nothing comes out (no generated output, no error message of any kind, etc.). Nothing is put in the Event Viewer/Application log either. I am stumped as to why I am not getting any output.</p>
<p>Is there any more information I can give to help? Here is the contents of one of my converted .csproj files (trimmed slightly to hide most of our source code file names):</p>
<p><?xml version="1.0" encoding="utf-8"?><br />
<Project ToolsVersion="4.0" DefaultTargets="Build" xmlns=" schemas.microsoft.com/developer/msbuild/2003 "><br />
  <PropertyGroup><br />
    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration><br />
    <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform><br />
    <ProductVersion>9.0.30729</ProductVersion><br />
    <SchemaVersion>2.0</SchemaVersion><br />
    <ProjectGuid>{13C244B1-E0E7-41FD-9118-D2CD8A567102}</ProjectGuid><br />
    <OutputType>Library</OutputType><br />
    <AppDesignerFolder>Properties</AppDesignerFolder><br />
    <RootNamespace>ArtOfTest.Common.Design</RootNamespace><br />
    <AssemblyName>ArtOfTest.Common.Design</AssemblyName><br />
    <TargetFrameworkVersion>v3.5</TargetFrameworkVersion><br />
    <FileAlignment>512</FileAlignment><br />
    <SccProjectName><br />
    </SccProjectName><br />
    <SccLocalPath><br />
    </SccLocalPath><br />
    <SccAuxPath><br />
    </SccAuxPath><br />
    <SccProvider><br />
    </SccProvider><br />
    <SignAssembly>true</SignAssembly><br />
    <AssemblyOriginatorKeyFile>ArtOfTest.Common.Design.snk</AssemblyOriginatorKeyFile><br />
    <ExpressionBlendVersion>3.0.1927.0</ExpressionBlendVersion><br />
    <FileUpgradeFlags><br />
    </FileUpgradeFlags><br />
    <OldToolsVersion>3.5</OldToolsVersion><br />
    <UpgradeBackupLocation /><br />
    <IsWebBootstrapper>false</IsWebBootstrapper><br />
    <PublishUrl>publish\</PublishUrl><br />
    <Install>true</Install><br />
    <InstallFrom>Disk</InstallFrom><br />
    <UpdateEnabled>false</UpdateEnabled><br />
    <UpdateMode>Foreground</UpdateMode><br />
    <UpdateInterval>7</UpdateInterval><br />
    <UpdateIntervalUnits>Days</UpdateIntervalUnits><br />
    <UpdatePeriodically>false</UpdatePeriodically><br />
    <UpdateRequired>false</UpdateRequired><br />
    <MapFileExtensions>true</MapFileExtensions><br />
    <ApplicationRevision>0</ApplicationRevision><br />
    <ApplicationVersion>1.0.0.%2a</ApplicationVersion><br />
    <UseApplicationTrust>false</UseApplicationTrust><br />
    <BootstrapperEnabled>true</BootstrapperEnabled><br />
  </PropertyGroup><br />
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' "><br />
    <DebugSymbols>true</DebugSymbols><br />
    <DebugType>full</DebugType><br />
    <Optimize>false</Optimize><br />
    <OutputPath>bin\Debug\</OutputPath><br />
    <DefineConstants>DEBUG;TRACE</DefineConstants><br />
    <ErrorReport>prompt</ErrorReport><br />
    <WarningLevel>4</WarningLevel><br />
  </PropertyGroup><br />
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' "><br />
    <DebugType>pdbonly</DebugType><br />
    <Optimize>true</Optimize><br />
    <OutputPath>bin\Release\</OutputPath><br />
    <DefineConstants><br />
    </DefineConstants><br />
    <ErrorReport>prompt</ErrorReport><br />
    <WarningLevel>4</WarningLevel><br />
  </PropertyGroup><br />
  <ItemGroup><br />
    <Reference Include="ArtOfTest.Common, Version=2.0.8.0, Culture=neutral, PublicKeyToken=14a0200bfcbb7b62, processorArchitecture=MSIL"><br />
      <SpecificVersion>False</SpecificVersion><br />
      <HintPath>..\..\..\..\..\..\..\..\..\..\Windows\assembly\GAC_MSIL\ArtOfTest.Common\2.0.8.0__14a0200bfcbb7b62\ArtOfTest.Common.dll</HintPath><br />
    </Reference><br />
    <Reference Include="PresentationCore"><br />
      <RequiredTargetFramework>3.0</RequiredTargetFramework><br />
    </Reference><br />
    <Reference Include="PresentationFramework"><br />
      <RequiredTargetFramework>3.0</RequiredTargetFramework><br />
    </Reference><br />
    <Reference Include="PresentationFramework.Aero"><br />
      <RequiredTargetFramework>3.0</RequiredTargetFramework><br />
    </Reference><br />
    <Reference Include="System" /><br />
    <Reference Include="System.Core"><br />
      <RequiredTargetFramework>3.5</RequiredTargetFramework><br />
    </Reference><br />
    <Reference Include="System.Drawing" /><br />
    <Reference Include="System.Runtime.Serialization"><br />
      <RequiredTargetFramework>3.0</RequiredTargetFramework><br />
    </Reference><br />
    <Reference Include="System.ServiceModel"><br />
      <RequiredTargetFramework>3.0</RequiredTargetFramework><br />
    </Reference><br />
    <Reference Include="System.Windows.Forms" /><br />
    <Reference Include="System.Xml.Linq"><br />
      <RequiredTargetFramework>3.5</RequiredTargetFramework><br />
    </Reference><br />
    <Reference Include="System.Data.DataSetExtensions"><br />
      <RequiredTargetFramework>3.5</RequiredTargetFramework><br />
    </Reference><br />
    <Reference Include="System.Data" /><br />
    <Reference Include="System.Xml" /><br />
    <Reference Include="UIAutomationProvider"><br />
      <RequiredTargetFramework>3.0</RequiredTargetFramework><br />
    </Reference><br />
    <Reference Include="WindowsBase"><br />
      <RequiredTargetFramework>3.0</RequiredTargetFramework><br />
    </Reference><br />
  </ItemGroup><br />
  <ItemGroup><br />
    <Compile Include="Data\CustomizableDataTable.cs"><br />
      <SubType>Component</SubType><br />
    </Compile><br />
    <Compile Include="ProjectModel\__enums.cs" /><br />
    <Compile Include="Properties\Resources.Designer.cs"><br />
      <AutoGen>True</AutoGen><br />
      <DesignTime>True</DesignTime><br />
      <DependentUpon>Resources.resx</DependentUpon><br />
    </Compile><br />
    <Compile Include="StringUtils.cs" /><br />
    <Compile Include="Translation\IdentificationDescriptorList.cs" /><br />
    <Compile Include="UI\General\GetString.Designer.cs"><br />
      <DependentUpon>GetString.cs</DependentUpon><br />
    </Compile><br />
  </ItemGroup><br />
  <ItemGroup><br />
    <EmbeddedResource Include="Properties\Resources.resx"><br />
      <Generator>ResXFileCodeGenerator</Generator><br />
      <LastGenOutput>Resources.Designer.cs</LastGenOutput><br />
    </EmbeddedResource><br />
    <EmbeddedResource Include="UI\General\GetString.resx"><br />
      <DependentUpon>GetString.cs</DependentUpon><br />
    </EmbeddedResource><br />
    <EmbeddedResource Include="UI\TypeEditors\DataDrivenPropertyEditorControl.resx"><br />
      <DependentUpon>DataDrivenPropertyEditorControl.cs</DependentUpon><br />
      <SubType>Designer</SubType><br />
    </EmbeddedResource><br />
  </ItemGroup><br />
  <ItemGroup><br />
    <None Include="ArtOfTest.Common.Design.snk" /><br />
  </ItemGroup><br />
  <ItemGroup><br />
    <Page Include="UI\FindExpression\FindClauseEditor.xaml"><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
    </Page><br />
    <Page Include="UI\FindExpression\FindExpressionEditor.xaml"><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
    </Page><br />
    <Page Include="UI\Sentence\SentencePreviewList.xaml"><br />
      <SubType>Designer</SubType><br />
      <Generator>MSBuild:Compile</Generator><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
    </Page><br />
  </ItemGroup><br />
  <ItemGroup><br />
    <Resource Include="Resources\Delete.png" /><br />
    <Resource Include="Resources\DomExplorer.png" /><br />
    <Resource Include="Resources\Fail.png" /><br />
    <Resource Include="Resources\ParamArrowDown.png" /><br />
    <Resource Include="Resources\Pass.png" /><br />
    <Resource Include="Resources\Validate.png" /><br />
  </ItemGroup><br />
  <ItemGroup><br />
    <Resource Include="Resources\AND.png" /><br />
    <Resource Include="Resources\button_accept.png" /><br />
    <Resource Include="Resources\icon_checkmark.off.png" /><br />
    <Resource Include="Resources\icon_checkmark.on.png" /><br />
    <Resource Include="Resources\icon_dropArrow.hover.png" /><br />
    <Resource Include="Resources\icon_dropArrow.opened.png" /><br />
    <Resource Include="Resources\icon_dropArrow.png" /><br />
    <Resource Include="Resources\icon_editPencil.png" /><br />
    <Resource Include="Resources\icon_locateDOM.on.png" /><br />
    <Resource Include="Resources\icon_locateDOM.png" /><br />
    <Resource Include="Resources\icon_resizer.png" /><br />
    <Resource Include="Resources\icon_verify.on.png" /><br />
    <Resource Include="Resources\icon_verify.png" /><br />
    <Resource Include="Resources\THEN.png" /><br />
  </ItemGroup><br />
  <ItemGroup><br />
    <None Include="Resources\datadriveneditor.png" /><br />
    <Page Include="UI\Sentence\SentenceParamUI3D.xaml"><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
    </Page><br />
    <Page Include="UI\Sentence\SentenceUI3D.xaml"><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
    </Page><br />
    <Page Include="UI\Sentence\VerificationBuilderResources.xaml"><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
      <Generator>MSBuild:Compile</Generator><br />
      <SubType>Designer</SubType><br />
    </Page><br />
  </ItemGroup><br />
  <ItemGroup><br />
    <BootstrapperPackage Include="Microsoft.Net.Client.3.5"><br />
      <Visible>False</Visible><br />
      <ProductName>.NET Framework 3.5 SP1 Client Profile</ProductName><br />
      <Install>false</Install><br />
    </BootstrapperPackage><br />
    <BootstrapperPackage Include="Microsoft.Net.Framework.3.5.SP1"><br />
      <Visible>False</Visible><br />
      <ProductName>.NET Framework 3.5 SP1</ProductName><br />
      <Install>true</Install><br />
    </BootstrapperPackage><br />
    <BootstrapperPackage Include="Microsoft.VisualBasic.PowerPacks.10.0"><br />
      <Visible>False</Visible><br />
      <ProductName>Microsoft Visual Basic PowerPacks 10.0</ProductName><br />
      <Install>true</Install><br />
    </BootstrapperPackage><br />
    <BootstrapperPackage Include="Microsoft.Windows.Installer.3.1"><br />
      <Visible>False</Visible><br />
      <ProductName>Windows Installer 3.1</ProductName><br />
      <Install>true</Install><br />
    </BootstrapperPackage><br />
  </ItemGroup><br />
  <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" /><br />
  <!-- To modify your build process, add your task inside one of the targets below and uncomment it.
      Other similar extension points exist, see Microsoft.Common.targets.
  <Target Name="BeforeBuild">
  </Target>
  <Target Name="AfterBuild">
  </Target>
  --><br />
  <PropertyGroup><br />
    <PostBuildEvent>if $(ConfigurationName)==Debug &#8220;C:\Program Files\Microsoft SDKs\Windows\v6.0a\bin\gacutil.exe&#8221; /i $(TargetPath)</PostBuildEvent><br />
  </PropertyGroup><br />
</Project></p>
<p><strong>InstallerGeek replied the topic: Re: heat.exe</strong><br />
I&#8217;ve found HEAT doesn&#8217;t generate any output even for a brand new empty VS2010 C# class library project. Here is what the output window contains when I try to build a simple installer containing only the brand new empty VS2010 C# class library project:</p>
<p><strong>InstallerExpert replied the topic: Re: heat.exe</strong><br />
I see two directories listed below. You should only have one.</p>
<p>&#8220;C:\Program Files\Windows Installer XML v3\bin\heat.exe&#8221; dir  &#8220;..\..\~tmp\j2build3v_win\apps&#8221; -gg -sfrag -scom -sreg &#8220;$(ProjectDir)..\..\..\~tmp\j2build3v_win\apps\eu&#8221; -out &#8220;$(ProjectDir)gen_fragment.wxs&#8221; -template:fragment</p>
<p>Should be:<br />
&#8220;C:\Program Files\Windows Installer XML v3\bin\heat.exe&#8221; dir  &#8220;..\..\~tmp\j2build3v_win\apps&#8221; -gg -sfrag -scom -sreg -out &#8220;$(ProjectDir)gen_fragment.wxs&#8221; -template:fragment</p>
<p>OR:</p>
<p>&#8220;C:\Program Files\Windows Installer XML v3\bin\heat.exe&#8221; dir &#8220;$(ProjectDir)..\..\..\~tmp\j2build3v_win\apps\eu&#8221; -gg -sfrag -scom -sreg -out &#8220;$(ProjectDir)gen_fragment.wxs&#8221; -template:fragment</p>
<p><strong>InstallerGeek replied the topic: Re: heat.exe</strong><br />
Is there a particular reason why Heat.exe is targeted and compiled specifically against the x86 architecture? I have seen a couple of questions about this around on the Internet but no firm answer or resolution. I briefly looked over the Heat code (v3.0.5419.0) and there does not seem to be anything specific that jumps out as being 64-bit incompatible. Then again, it was more a cursory glance than a walkthrough.</p>
<p>I am currently migrating our build and development environments to 64-bit. In this process, I&#8217;d also like to migrate our current setup projects to MSBuild using the WiX targets and the HeatProject task. I may try my hand at compiling the Heat project for 64-bit process architectures if that&#8217;s what it comes down to. Any help before it gets ugly would be much appreciated!</p>
<p>By the way, using a 64-bit version of MSBuild yields the expected BadImageFormatException from heat.exe.</p>
<p><strong>InstallerExpert replied the topic: Re: heat.exe</strong><br />
On 1/13/2010 8:07 PM, Navid Azimi-Garakani wrote:<br />
> Is there a particular reason why Heat.exe is targeted and compiled specifically against the x86 architecture?</p>
<p>Because an MSIL .exe runs as a 64-bit process on an x64 system, so it couldn&#8217;t load x86 DLLs. I suspect there&#8217;s a need for Heat64.</p>
<p>> I may try my hand at compiling the Heat project for 64-bit process architectures if that&#8217;s what it comes down to. Any help before it gets ugly would be much appreciated!<br />
>   </p>
<p>Should be pretty straightforward, just get an enlistment.</p>
<p><strong>InstallerGeek replied the topic: Re: heat.exe</strong><br />
Not sure if it is that straight forward. I think the reason we keep punting this feature is the dependencies heat.exe has on the Wix core project (<br />
<a href="http://sourceforge.net/tracker/index.php?func=d...d=105970&#038;atid=642717">sourceforge.net/tracker/index.php?func=d&#8230;d=105970&#038;atid=642717 </a><br />
).</p>
<p>The post <a href="https://www.scmgalaxy.com/tutorials/heat-exe/">Heat.exe</a> appeared first on <a href="https://www.scmgalaxy.com/tutorials">scmGalaxy</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.scmgalaxy.com/tutorials/heat-exe/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
