Re: [WiX-users] One patch to rule them all
I tried removing the DLL from the admin upgrade image, but since the patch was still created with different baseline(v1) images (same GUIDs, just one different file), it fails when applying the patch. Chad, you're kind of talking over my head. Could you be a little more verbose with your suggestion and apply it to my situation? You think I should have a base installer without the DLL? Then create V2/V3 upgrades with the DLL? What do I apply the patch against? (as you can see, im confused) > Date: Tue, 4 Nov 2008 12:34:08 -0500> From: [EMAIL PROTECTED]> To: > 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> between the baselined msi and a daily msi.> > Thanks > though.> > On Tue, Nov 4, 2008 at 12:25 PM, Bryan Turner <[EMAIL > PROTECTED]>wrote:> > > Chad,> >> > I may not be fully understanding your > requirements, but it sounds like you> > want to create a patch that does not > patch every file in the installer? I> > have not yet tried to create patches > with WIX, I still use msimsp to create> > patches with a .pcp file for the > input, so I cant tell you the WIX way to> > create the patch that ignores > this file, but I assume this process will work> > for both since it is > outside the patch creation process.> >> > What you can do is to create your > Target image and your Upgrade image, and> > then simply delete the file that > you don't want patched from the> > administrative Upgrade image and it won't > be included in the patch. You do> > not need to modify your installer .msi in > any way, or change the .pcp to> > ignore the file. Just deleting the file > from disk in the administrative> > 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 patch to rule them all> >> > I'm not a patching expert, > but there is a feature in pyro that allows you> > to filter out Fragments and > target only the portions of the install that you> > want.> >> > -Original > Message-> > From: Rob Lange [mailto:[EMAIL PROTECTED]> > Sent: Monday, > November 03, 2008 22:09> > To: 'General discussion 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 me being able > to ask WiX to please ignore the DLL and> > just patch my other files, no > matter how different the DLL is from the V2> > or> > V1 of my installer the > patch was created from.> >> > I have other ugly/non-professional/hack non-WiX > solutions, but getting that> > code reviewed is an ugly prospect.> >> > > -Original Message-> > From: Chad Miles [mailto:[EMAIL PROTECTED]> > > Sent: Monday, November 03, 2008 8: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 else's word though. Just an opening > thought.> >> > If you want it included no matter what (as you stated), maybe > script based> > on file version?> >> > On Mon, Nov 3, 2008 at 10:00 PM, Rob > Lange <[EMAIL PROTECTED]> wrote:> >> > >> > > I have a strange question that > I've been trying to find a solution to for> > > awhile and I'm hoping people > who work with WiX more than me might have a> > > good suggestion. I've got an > installer that is built every day, using> > WiX,> > > that contains a DLL > taken from a project in development. I also have a> > > patch, built using > WiX, for the installer that adds a few files to the> > > program. The patch > is hoste
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 between the baselined msi and a daily msi. Thanks though. On Tue, Nov 4, 2008 at 12:25 PM, Bryan Turner <[EMAIL PROTECTED]>wrote: > Chad, > > I may not be fully understanding your requirements, but it sounds like you > want to create a patch that does not patch every file in the installer? I > have not yet tried to create patches with WIX, I still use msimsp to create > patches with a .pcp file for the input, so I cant tell you the WIX way to > create the patch that ignores this file, but I assume this process will work > for both since it is outside the patch creation process. > > What you can do is to create your Target image and your Upgrade image, and > then simply delete the file that you don't want patched from the > administrative Upgrade image and it won't be included in the patch. You do > not need to modify your installer .msi in any way, or change the .pcp to > ignore the file. Just deleting the file from disk in the administrative > 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 patch to rule them all > > I'm not a patching expert, but there is a feature in pyro that allows you > to filter out Fragments and target only the portions of the install that you > want. > > -Original Message- > From: Rob Lange [mailto:[EMAIL PROTECTED] > Sent: Monday, November 03, 2008 22:09 > To: 'General discussion 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 me being able to ask WiX to please ignore the DLL and > just patch my other files, no matter how different the DLL is from the V2 > or > V1 of my installer the patch was created from. > > I have other ugly/non-professional/hack non-WiX solutions, but getting that > code reviewed is an ugly prospect. > > -Original Message- > From: Chad Miles [mailto:[EMAIL PROTECTED] > Sent: Monday, November 03, 2008 8: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 else's word though. Just an opening thought. > > If you want it included no matter what (as you stated), maybe script based > on file version? > > On Mon, Nov 3, 2008 at 10:00 PM, Rob Lange <[EMAIL PROTECTED]> wrote: > > > > > I have a strange question that I've been trying to find a solution to for > > awhile and I'm hoping people who work with WiX more than me might have a > > good suggestion. I've got an installer that is built every day, using > WiX, > > that contains a DLL taken from a project in development. I also have a > > patch, built using WiX, for the installer that adds a few files to the > > program. The patch is hosted on a server that our feature fetches the > > location to then downloads and installs the patch. The problem is that > the > > patch will only work for that day's build because the DLL constantly > > changes. I need to find a way to include this DLL in the installer > package, > > but not have the patch care that the DLL has changed. So, *gulp* is this > > possible with WiX? > > - > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > challenge > > Build the coolest Linux based applications with Moblin SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event anywhere in the > world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based ap
Re: [WiX-users] One patch to rule them all
Chad, I may not be fully understanding your requirements, but it sounds like you want to create a patch that does not patch every file in the installer? I have not yet tried to create patches with WIX, I still use msimsp to create patches with a .pcp file for the input, so I cant tell you the WIX way to create the patch that ignores this file, but I assume this process will work for both since it is outside the patch creation process. What you can do is to create your Target image and your Upgrade image, and then simply delete the file that you don't want patched from the administrative Upgrade image and it won't be included in the patch. You do not need to modify your installer .msi in any way, or change the .pcp to ignore the file. Just deleting the file from disk in the administrative 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 patch to rule them all I'm not a patching expert, but there is a feature in pyro that allows you to filter out Fragments and target only the portions of the install that you want. -Original Message- From: Rob Lange [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2008 22:09 To: 'General discussion 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 me being able to ask WiX to please ignore the DLL and just patch my other files, no matter how different the DLL is from the V2 or V1 of my installer the patch was created from. I have other ugly/non-professional/hack non-WiX solutions, but getting that code reviewed is an ugly prospect. -Original Message- From: Chad Miles [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2008 8: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 else's word though. Just an opening thought. If you want it included no matter what (as you stated), maybe script based on file version? On Mon, Nov 3, 2008 at 10:00 PM, Rob Lange <[EMAIL PROTECTED]> wrote: > > I have a strange question that I've been trying to find a solution to for > awhile and I'm hoping people who work with WiX more than me might have a > good suggestion. I've got an installer that is built every day, using WiX, > that contains a DLL taken from a project in development. I also have a > patch, built using WiX, for the installer that adds a few files to the > program. The patch is hosted on a server that our feature fetches the > location to then downloads and installs the patch. The problem is that the > patch will only work for that day's build because the DLL constantly > changes. I need to find a way to include this DLL in the installer package, > but not have the patch care that the DLL has changed. So, *gulp* is this > possible with WiX? > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?bann
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 to filter out Fragments and target only the portions of the install that you want. -Original Message- From: Rob Lange [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2008 22:09 To: 'General discussion 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 me being able to ask WiX to please ignore the DLL and just patch my other files, no matter how different the DLL is from the V2 or V1 of my installer the patch was created from. I have other ugly/non-professional/hack non-WiX solutions, but getting that code reviewed is an ugly prospect. -Original Message- From: Chad Miles [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2008 8: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 else's word though. Just an opening thought. If you want it included no matter what (as you stated), maybe script based on file version? On Mon, Nov 3, 2008 at 10:00 PM, Rob Lange <[EMAIL PROTECTED]> wrote: > > I have a strange question that I've been trying to find a solution to for > awhile and I'm hoping people who work with WiX more than me might have a > good suggestion. I've got an installer that is built every day, using WiX, > that contains a DLL taken from a project in development. I also have a > patch, built using WiX, for the installer that adds a few files to the > program. The patch is hosted on a server that our feature fetches the > location to then downloads and installs the patch. The problem is that the > patch will only work for that day's build because the DLL constantly > changes. I need to find a way to include this DLL in the installer package, > but not have the patch care that the DLL has changed. So, *gulp* is this > possible with WiX? > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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 me being able to ask WiX to please ignore the DLL and just patch my other files, no matter how different the DLL is from the V2 or V1 of my installer the patch was created from. I have other ugly/non-professional/hack non-WiX solutions, but getting that code reviewed is an ugly prospect. -Original Message- From: Chad Miles [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2008 8: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 else's word though. Just an opening thought. If you want it included no matter what (as you stated), maybe script based on file version? On Mon, Nov 3, 2008 at 10:00 PM, Rob Lange <[EMAIL PROTECTED]> wrote: > > I have a strange question that I've been trying to find a solution to for > awhile and I'm hoping people who work with WiX more than me might have a > good suggestion. I've got an installer that is built every day, using WiX, > that contains a DLL taken from a project in development. I also have a > patch, built using WiX, for the installer that adds a few files to the > program. The patch is hosted on a server that our feature fetches the > location to then downloads and installs the patch. The problem is that the > patch will only work for that day's build because the DLL constantly > changes. I need to find a way to include this DLL in the installer package, > but not have the patch care that the DLL has changed. So, *gulp* is this > possible with WiX? > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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 else's word though. Just an opening thought. If you want it included no matter what (as you stated), maybe script based on file version? On Mon, Nov 3, 2008 at 10:00 PM, Rob Lange <[EMAIL PROTECTED]> wrote: > > I have a strange question that I've been trying to find a solution to for > awhile and I'm hoping people who work with WiX more than me might have a > good suggestion. I've got an installer that is built every day, using WiX, > that contains a DLL taken from a project in development. I also have a > patch, built using WiX, for the installer that adds a few files to the > program. The patch is hosted on a server that our feature fetches the > location to then downloads and installs the patch. The problem is that the > patch will only work for that day's build because the DLL constantly > changes. I need to find a way to include this DLL in the installer package, > but not have the patch care that the DLL has changed. So, *gulp* is this > possible with WiX? > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] One patch to rule them all
I have a strange question that I’ve been trying to find a solution to for awhile and I’m hoping people who work with WiX more than me might have a good suggestion. I’ve got an installer that is built every day, using WiX, that contains a DLL taken from a project in development. I also have a patch, built using WiX, for the installer that adds a few files to the program. The patch is hosted on a server that our feature fetches the location to then downloads and installs the patch. The problem is that the patch will only work for that day’s build because the DLL constantly changes. I need to find a way to include this DLL in the installer package, but not have the patch care that the DLL has changed. So, *gulp* is this possible with WiX? - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
