[WiX-users] Re: Repair from Add or Remove Programs

[Rob H. <ro...@sn...>]

I thought Windows just cached the logic, and not the files, of the MSI. 
  Is that not right?  If not, you'd end up using a lot of disc space. 
Isn't this why you need to original MSI for any actions that need to 
write/replace files?

Rob

Rob Mensching wrote:
> Get a verbose log file for your repair (the logging registry key 
> documented in the MSI SDK works well). 
> 
>  
> 
> In that log file you should see a message that explains why the Windows 
> Installer thought it needed the original source media.  Usually, because 
> it suspected one of your files was broken and needed repair (you’re not 
> one of those people putting bogus file versions in the File table are 
> you?  <smile/>).
> 
>  
> 
> ------------------------------------------------------------------------
> 
> *From:* wix...@li... 
> [mailto:wix...@li...] *On Behalf Of *Brian Simoneau
> *Sent:* Thursday, October 27, 2005 2:47 PM
> *To:* wix...@li...
> *Subject:* [WiX-users] Repair from Add or Remove Programs
> 
>  
> 
> After I have installed my product, I look at its entry in Add or Remove 
> Programs.  From here I can attempt to Repair the product.  However, 
> during the repair a message comes up asking me for the original msi.  I 
> thought that Add or Remove Programs used a cached version of the msi.  
> The user is doesn't have access to the original msi since our installer 
> wraps the msi in a bootstrapper so that the appropriate command line 
> arguments can be passed to msiexec.  Is this the expected behavior for 
> repair?  Note that the same thing happens if trying to add a new feature 
> to the product, but everything works fine during uninstall or when 
> removing features from the product.
> 
>  
> 
> Brian Simoneau
> 
> Software Developer
> 
> Freedom Scientific
> 
>  
>