:
> wix-users@lists.sourceforge.net> Subject: Re: [WiX-users] One patch to rule
> them all> > Oh no, I'm not asking for help. I was offering a few suggestions
> to the> original poster.> > Baselining the msi is the way we do it, and do a
> diff/patch validation>
gt; Upgrade image will prevent it from being included in the patch.
>
>
> -Original Message-
> From: Rob Mensching [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 03, 2008 10:28 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] One pa
--Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Monday, November 03, 2008 10:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] One patch to rule them all
I'm not a patching expert, but there is a feature in pyro that allows you
ussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] One patch to rule them all
I assume the patch fails because it was created with an installer set (both
base[v1] and upgrade[v2]) that had a different DLL than the current
installer being used on the machine.
It all comes down to m
:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] One patch to rule them all
Could you baseline a Patch Target msi and patch off that?
I'm not big on patching, but it sounds like the msp is baselined and not the
msi.
I'd definitely take someone e
Could you baseline a Patch Target msi and patch off that?
I'm not big on patching, but it sounds like the msp is baselined and not the
msi.
I'd definitely take someone else's word though. Just an opening thought.
If you want it included no matter what (as you stated), maybe script based
on file
6 matches
Mail list logo
