Re: [WiX-users] preventing the overwrite of Shortcut
John Vottero wrote: > I believe that a major upgrade is essentially an uninstall of the old > version followed by an install of the new version. > It depends on the scheduling of RemoveExistingProducts. If it's early, then the new product is installed (bumping up ref counts) and then the old product is removed (bumping down ref counts and removing components that were only in the old product). -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] preventing the overwrite of Shortcut
I believe that a major upgrade is essentially an uninstall of the old
version followed by an install of the new version.
I *think* you can get the effect you want by sequencing RemoveShortcuts
after CreateShortcuts but, I don't know what side effects you have to
watch out for.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of Jeff Paulsen
> Sent: Tuesday, June 19, 2007 1:58 PM
> To: 'Rob Mensching'; [EMAIL PROTECTED]; wix-
> [EMAIL PROTECTED]
> Subject: Re: [WiX-users] preventing the overwrite of Shortcut
>
> Certainly there are better places for configuration data. The
advantage
> to
> command-line options is that you can edit them without starting the
> application, so to keep that benefit, I'd have to provide a separate
> configuration tool. I'm not opposed to doing that later this week, but
> having shortcuts that live through an upgrade will make my customer
> happy
> tonight.
>
> It seemed that setting NeverOverwrite on the Component element was
> simpler.
>
> I just can't figure out why my shortcut would be overwritten during an
> upgrade anyway. The guid hasn't changed. The keypath hasn't changed.
> Does
> anybody know why this doesn't do what I expected?
>
> Jeff Paulsen
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:wix-users-
> > [EMAIL PROTECTED] On Behalf Of Rob Mensching
> > Sent: Tuesday, June 19, 2007 10:11 AM
> > To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] preventing the overwrite of Shortcut
> >
> > Beyond what Richard suggests below, you'll have to write a block of
> > custom code to do the migration of user data. Possible but mostly
> > annoying.
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:wix-users-
> > [EMAIL PROTECTED] On Behalf Of
> > [EMAIL PROTECTED]
> > Sent: Tuesday, June 19, 2007 10:02 AM
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] preventing the overwrite of Shortcut
> >
> > I think my question would be why the user is forced into a (somewhat
> > unfriendly) specification of command line parameters as opposed to a
> > friendlier scenario using (for example) a configuration file, or a
> > configuration interface that stores things somewhere appropriate.
> >
> > You may want to take a closer look at the design here. What is the
> > user
> > specifying via the shortcut which can apparently not be handled
> > through
> > a better mechanism?
> >
> > Just my $.02.
> >
> > Regards,
> > Richard
> >
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Jeff
> > Paulsen
> > Sent: Tuesday, June 19, 2007 12:39 PM
> > To: wix-users@lists.sourceforge.net
> > Subject: [WiX-users] preventing the overwrite of Shortcut
> >
> > I have a Wix installer that includes something like this:
> >
> >> Guid="{someguid}">
> > > Key="Software\TheCompany\TheProduct 1.0\My" Root="HKCU">
> >> Name="MyShortcuts" Type="string" Value="present" />
> >
> > > Name="TheProduct 1.0" Icon="TheProduct.exe" IconIndex="0"
> > WorkingDirectory="INSTALLLOCATION" Advertise="no"
> > Target="[#TheProduct.exe]"
> > />
> > > Name="TheProduct
> > 1.0" Icon="TheProduct.exe" IconIndex="0"
> > WorkingDirectory="INSTALLLOCATION"
> > Advertise="no" Target="[#TheProduct.exe]" />
> >
> >
> > After installation, my users frequently add command-line flags to
the
> > shortcut. When they upgrade to a new version, their shortcuts are
> > overwritten, losing the command-line flags. I added the
> > NeverOverwrite
> > attribute to the Component, but it didn't have any effect.
> >
> > All my upgrades are done with Product Id="*", so they're all "major"
> > upgrades.
> >
> > Am I doing something wrong with my Wix? Failing that, is there any
> > reasonable way to preserve the command-line parameters my users have
> > added
> > to the shortcut?
> >
> > Thanks,
> > Jeff Paulsen
> >
> >
> >
-
> > ---
> > -
> > This SF.net email is sponsored by DB2
Re: [WiX-users] preventing the overwrite of Shortcut
Certainly there are better places for configuration data. The advantage to
command-line options is that you can edit them without starting the
application, so to keep that benefit, I'd have to provide a separate
configuration tool. I'm not opposed to doing that later this week, but
having shortcuts that live through an upgrade will make my customer happy
tonight.
It seemed that setting NeverOverwrite on the Component element was simpler.
I just can't figure out why my shortcut would be overwritten during an
upgrade anyway. The guid hasn't changed. The keypath hasn't changed. Does
anybody know why this doesn't do what I expected?
Jeff Paulsen
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of Rob Mensching
> Sent: Tuesday, June 19, 2007 10:11 AM
> To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] preventing the overwrite of Shortcut
>
> Beyond what Richard suggests below, you'll have to write a block of
> custom code to do the migration of user data. Possible but mostly
> annoying.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: Tuesday, June 19, 2007 10:02 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] preventing the overwrite of Shortcut
>
> I think my question would be why the user is forced into a (somewhat
> unfriendly) specification of command line parameters as opposed to a
> friendlier scenario using (for example) a configuration file, or a
> configuration interface that stores things somewhere appropriate.
>
> You may want to take a closer look at the design here. What is the
> user
> specifying via the shortcut which can apparently not be handled
> through
> a better mechanism?
>
> Just my $.02.
>
> Regards,
> Richard
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jeff
> Paulsen
> Sent: Tuesday, June 19, 2007 12:39 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] preventing the overwrite of Shortcut
>
> I have a Wix installer that includes something like this:
>
>Guid="{someguid}">
> Key="Software\TheCompany\TheProduct 1.0\My" Root="HKCU">
>Name="MyShortcuts" Type="string" Value="present" />
>
> Name="TheProduct 1.0" Icon="TheProduct.exe" IconIndex="0"
> WorkingDirectory="INSTALLLOCATION" Advertise="no"
> Target="[#TheProduct.exe]"
> />
> Name="TheProduct
> 1.0" Icon="TheProduct.exe" IconIndex="0"
> WorkingDirectory="INSTALLLOCATION"
> Advertise="no" Target="[#TheProduct.exe]" />
>
>
> After installation, my users frequently add command-line flags to the
> shortcut. When they upgrade to a new version, their shortcuts are
> overwritten, losing the command-line flags. I added the
> NeverOverwrite
> attribute to the Component, but it didn't have any effect.
>
> All my upgrades are done with Product Id="*", so they're all "major"
> upgrades.
>
> Am I doing something wrong with my Wix? Failing that, is there any
> reasonable way to preserve the command-line parameters my users have
> added
> to the shortcut?
>
> Thanks,
> Jeff Paulsen
>
>
> -
> ---
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> * C O N F I D E N T I A L I T Y N O T I C E *
> ---
> The content of this e-mail is intended solely for the use of the
> individual or entity to whom it is addressed. If you have received
> this communication in error, be aware that forwarding it, copying it,
> or in any way disclosing its content to any other person, is strictly
> prohibited. Quixote Traffic Corporation is neither liable for the
> contents, nor for the proper, complete and timely transmission of
> (the information contained in) this communication. If you have
> received this communication in error, please notify the auth
Re: [WiX-users] preventing the overwrite of Shortcut
Beyond what Richard suggests below, you'll have to write a block of custom code to do the migration of user data. Possible but mostly annoying. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, June 19, 2007 10:02 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] preventing the overwrite of Shortcut I think my question would be why the user is forced into a (somewhat unfriendly) specification of command line parameters as opposed to a friendlier scenario using (for example) a configuration file, or a configuration interface that stores things somewhere appropriate. You may want to take a closer look at the design here. What is the user specifying via the shortcut which can apparently not be handled through a better mechanism? Just my $.02. Regards, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Paulsen Sent: Tuesday, June 19, 2007 12:39 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] preventing the overwrite of Shortcut I have a Wix installer that includes something like this: After installation, my users frequently add command-line flags to the shortcut. When they upgrade to a new version, their shortcuts are overwritten, losing the command-line flags. I added the NeverOverwrite attribute to the Component, but it didn't have any effect. All my upgrades are done with Product Id="*", so they're all "major" upgrades. Am I doing something wrong with my Wix? Failing that, is there any reasonable way to preserve the command-line parameters my users have added to the shortcut? Thanks, Jeff Paulsen - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Quixote Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] preventing the overwrite of Shortcut
I think my question would be why the user is forced into a (somewhat unfriendly) specification of command line parameters as opposed to a friendlier scenario using (for example) a configuration file, or a configuration interface that stores things somewhere appropriate. You may want to take a closer look at the design here. What is the user specifying via the shortcut which can apparently not be handled through a better mechanism? Just my $.02. Regards, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Paulsen Sent: Tuesday, June 19, 2007 12:39 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] preventing the overwrite of Shortcut I have a Wix installer that includes something like this: After installation, my users frequently add command-line flags to the shortcut. When they upgrade to a new version, their shortcuts are overwritten, losing the command-line flags. I added the NeverOverwrite attribute to the Component, but it didn't have any effect. All my upgrades are done with Product Id="*", so they're all "major" upgrades. Am I doing something wrong with my Wix? Failing that, is there any reasonable way to preserve the command-line parameters my users have added to the shortcut? Thanks, Jeff Paulsen - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Quixote Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] preventing the overwrite of Shortcut
I have a Wix installer that includes something like this: After installation, my users frequently add command-line flags to the shortcut. When they upgrade to a new version, their shortcuts are overwritten, losing the command-line flags. I added the NeverOverwrite attribute to the Component, but it didn't have any effect. All my upgrades are done with Product Id="*", so they're all "major" upgrades. Am I doing something wrong with my Wix? Failing that, is there any reasonable way to preserve the command-line parameters my users have added to the shortcut? Thanks, Jeff Paulsen - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
