http://blogs.msdn.com/b/astebner/archive/2007/05/31/3012427.aspxI ran into an interesting scenario related to Windows Installer major upgrades recently and I wanted to summarize some things I learned from this experience and from the MSDN documentation in case they are useful for others. In the scenario I ran intoen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/astebner/archive/2007/05/31/3012427.aspx#9229832Wed, 17 Dec 2008 05:00:12 GMT91d46819-8472-40ad-a661-2c78acb4018c:9229832Aaron Stebner's WebLog<p>When I create an MSI-based installer, one of the things I typically include in the setup authoring is</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=9229832" width="1" height="1">http://blogs.msdn.com/b/astebner/archive/2007/05/31/3012427.aspx#4802488Fri, 07 Sep 2007 09:31:50 GMT91d46819-8472-40ad-a661-2c78acb4018c:4802488MSDN Blog Postings » Subtle problem with major upgrades in WiX files in the Media Center SDK<p>PingBack from <a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2007/09/07/subtle-problem-with-major-upgrades-in-wix-files-in-the-media-center-sdk-2/">http://msdnrss.thecoderblogs.com/2007/09/07/subtle-problem-with-major-upgrades-in-wix-files-in-the-media-center-sdk-2/</a></p><img src="http://blogs.msdn.com/aggbug.aspx?PostID=4802488" width="1" height="1">http://blogs.msdn.com/b/astebner/archive/2007/05/31/3012427.aspx#4799002Fri, 07 Sep 2007 05:49:13 GMT91d46819-8472-40ad-a661-2c78acb4018c:4799002Noticias externas<p>One of the features included in the WiX v3.0 source files included in the C# project template in the</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=4799002" width="1" height="1">http://blogs.msdn.com/b/astebner/archive/2007/05/31/3012427.aspx#4798338Fri, 07 Sep 2007 05:06:53 GMT91d46819-8472-40ad-a661-2c78acb4018c:4798338Aaron Stebner's WebLog<p>One of the features included in the WiX v3.0 source files included in the C# project template in the</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=4798338" width="1" height="1">http://blogs.msdn.com/b/astebner/archive/2007/05/31/3012427.aspx#4484252Mon, 20 Aug 2007 23:06:37 GMT91d46819-8472-40ad-a661-2c78acb4018c:4484252Aaron Stebner<p>Hi Sonaliagrawal - You will need to debug your application after installing the MSI to figure out why it is failing to launch. &nbsp;It is likely not able to find some of its dependent DLLs after you moved them to a new location, and you may need to revert that change or make some additional changes to your MSI to correct this problem.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=4484252" width="1" height="1">http://blogs.msdn.com/b/astebner/archive/2007/05/31/3012427.aspx#4405197Thu, 16 Aug 2007 00:43:01 GMT91d46819-8472-40ad-a661-2c78acb4018c:4405197sonaliagrawal<p>HI, I am Sonali and am not sure if this is the right place to ask this question, If its not, am sorry to bother you... I am working on a tool written in VB.NET. I added a setup project to it. The project ran fine untill I reorganized my reference dll's and other files to a different directory structure. Ever since then, the msi gets installed but app fails to launch. Please can you help me understand what is the problem and/or resolution?? </p> <p>Regards,</p> <p>Sonali</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=4405197" width="1" height="1">