<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: The case of the missing Mergemod.dll in WiX v3.0.4123</title>
	<atom:link href="http://www.joyofsetup.com/2008/05/27/the-case-of-the-missing-mergemoddll-in-wix-v304123/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joyofsetup.com/2008/05/27/the-case-of-the-missing-mergemoddll-in-wix-v304123/</link>
	<description>Bob Arnson's blog about setup and servicing</description>
	<lastBuildDate>Fri, 23 Jul 2010 01:04:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Christopher Painter</title>
		<link>http://www.joyofsetup.com/2008/05/27/the-case-of-the-missing-mergemoddll-in-wix-v304123/comment-page-1/#comment-6577</link>
		<dc:creator>Christopher Painter</dc:creator>
		<pubDate>Wed, 18 Jun 2008 03:36:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.joyofsetup.com/2008/05/27/the-case-of-the-missing-mergemoddll-in-wix-v304123/#comment-6577</guid>
		<description>I used to have this problem at Continental Airlines all the time because I had internal VB6 teams and external vendors that I was repackaging that just refused to follow proper versioning practices.  Ya, I know.. I tried to get them to change the ways but thems the breaks.

The problem was easily solved by `Always Overwrite` ( not AMUS... an InstallShield feature that increments the File table to the upperbound ) and I never saw any adverse effects.</description>
		<content:encoded><![CDATA[<p>I used to have this problem at Continental Airlines all the time because I had internal VB6 teams and external vendors that I was repackaging that just refused to follow proper versioning practices.  Ya, I know.. I tried to get them to change the ways but thems the breaks.</p>
<p>The problem was easily solved by `Always Overwrite` ( not AMUS&#8230; an InstallShield feature that increments the File table to the upperbound ) and I never saw any adverse effects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Arnson</title>
		<link>http://www.joyofsetup.com/2008/05/27/the-case-of-the-missing-mergemoddll-in-wix-v304123/comment-page-1/#comment-5774</link>
		<dc:creator>Bob Arnson</dc:creator>
		<pubDate>Tue, 03 Jun 2008 14:54:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.joyofsetup.com/2008/05/27/the-case-of-the-missing-mergemoddll-in-wix-v304123/#comment-5774</guid>
		<description>Alasdair,

With a bootstrapper/chainer, you could do the uninstall from it which would prevent the problem. The problem is during the major upgrade, MSI doesn&#039;t want to downgrade the file.</description>
		<content:encoded><![CDATA[<p>Alasdair,</p>
<p>With a bootstrapper/chainer, you could do the uninstall from it which would prevent the problem. The problem is during the major upgrade, MSI doesn&#8217;t want to downgrade the file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alasdair King</title>
		<link>http://www.joyofsetup.com/2008/05/27/the-case-of-the-missing-mergemoddll-in-wix-v304123/comment-page-1/#comment-5758</link>
		<dc:creator>Alasdair King</dc:creator>
		<pubDate>Tue, 03 Jun 2008 09:40:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.joyofsetup.com/2008/05/27/the-case-of-the-missing-mergemoddll-in-wix-v304123/#comment-5758</guid>
		<description>Hey, so what would be your take on how to best handle this situation?

1 Change the installer so it automagically uninstalls the old version before installing the new - need to stop it checking for old components to skip, too. Most Installer work.

2 Hack the old DLL to increase the version number, so you don&#039;t have to change your installer. Might need to re-sign the DLL. Least installer work, breaks DLL versioning.

3 Stop the installer installing if the old package is still installed. Most user pain.

4 Something else?</description>
		<content:encoded><![CDATA[<p>Hey, so what would be your take on how to best handle this situation?</p>
<p>1 Change the installer so it automagically uninstalls the old version before installing the new &#8211; need to stop it checking for old components to skip, too. Most Installer work.</p>
<p>2 Hack the old DLL to increase the version number, so you don&#8217;t have to change your installer. Might need to re-sign the DLL. Least installer work, breaks DLL versioning.</p>
<p>3 Stop the installer installing if the old package is still installed. Most user pain.</p>
<p>4 Something else?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
