Shawn Dwyer wrote:
> I worked with MS support and we believe we have resolved this issue.
> It came down to a bug in my original installer where my custom UI was
> being shown even when patches were applied. Apparently this was
> tweaking some feature states (although I don't know how or why,
I worked with MS support and we believe we have resolved this issue. It
came down to a bug in my original installer where my custom UI was being
shown even when patches were applied. Apparently this was tweaking some
feature states (although I don't know how or why, and the msiexec log didnt
show
Shawn Dwyer wrote:
> Thanks Bob. I couldn't seem to find a PatchFiles action in the log
> though, so perhaps that is the problem. Using Orca I applied my patch
> to the MSI and I don't see a PatchFiles in the InstallExecuteSequence
> table either. What would cause this not to be included? D
Bob Arnson wrote: check out the PatchFiles action to see what MSI
actually does.
Thanks Bob. I couldn't seem to find a PatchFiles action in the log though,
so perhaps that is the problem. Using Orca I applied my patch to the MSI
and I don't see a PatchFiles in the InstallExecuteSequenc
Shawn Dwyer wrote:
> below. In the example, NewFile.exe and NewFile.exe.config are both in the
> same Component, where NewFile.exe is the keyfile being upgraded from 3.0.37
> to 3.0.38, and NewFile.exe.config has new content but obviously no version
> number. The results I am seeing is that NewFi
Hi,
Using Wix 3.0.5315.0 I'm trying to create my first real (non-sample) MSP
following the instructions here:
http://blogs.msdn.com/pmarcu/archive/2008/05/30/Patching-something-you-didnt-build-with-WiX-using-WiX-.aspx
I created the admin image from version 3.0.37 of my app, copied it, and
replace
6 matches
Mail list logo
