Re: [WiX-users] Question on Patch Files.
Normally a patch just includes resources that have changed, plus any changes
from earlier patches - Patch families can only grow.
As far as I know, when you refer to a resource in the patch family, the whole
fragment that the resource belongs to is pulled into the patch. Therefore you
could refer to just one thing in each fragment that you want in your list and
you'd not need to change it in future.
I would examine the resulting patch to see how much it has included - I don't
know if unchanged resources have any effect on the patch although I'd assume
not.
You'll likely have to edit your patch wxs every time to change the patch
display name, client patch ID etc although these could be automated.
-Original Message-
From: Brian Lemke [mailto:brian.le...@apihealthcare.com]
Sent: 25 July 2011 23:22
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Question on Patch Files.
When building a Patch for a setup should a patch file contain all items that
could change or just the ones I know that have changed. For example I have
the following defined:
PatchFamily Id=SoftwareUpdates Version=$(var.PublicVersion)
Supersede=yes ProductCode={----}
PropertyRef Id=ProductName/
ComponentRef Id=RegistrySettings /
ComponentRef Id=File1 /
ComponentRef Id=File2 /
ComponentRef Id=File3 /
/PatchFamily
The two setups I have only differ by one file, say File1. Should I only
have in the patch file the components that I know are different? Does it
hurt to put these other components in the patch file even if they don't
change? I was asking because would it make sense to perhaps have one patch
file with everything that could be patched listed in it so I don't have to
create this file over and over again?
--Brian
This message (including any attachments) contains confidential and privileged
information intended for a specific purpose, and is protected by law. If you
are not the intended recipient, you must delete this message and any
attachments. You are hereby notified that any disclosure, copying, or
distribution of this message, or any attachments, or the taking of any action
based on it, is strictly prohibited. Opinions, conclusions, and other
information in this message that do not relate to the official business of
API Healthcare Corporation (API Healthcare) shall be understood as neither
given nor endorsed by API Healthcare.
API Healthcare Corporation
1550 Innovation Way
Hartford, WI 53027
-
-
Storage Efficiency Calculator
This modeling tool is based on patent-pending intellectual property that
has been used successfully in hundreds of IBM storage optimization engage-
ments, worldwide. Store less, Store more with what you own, Move data to
the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and we
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY,
UK.
--
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question on Patch Files.
Well, the whole point of a patch versus a major upgrade is it's smaller, so one
generally wants to include only the stuff that has changed. If you find
yourself wanting to throw more in, that may be a good sign that you might want
to do a major upgrade instead.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install Engineer - jXchange
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
-Original Message-
From: Brian Lemke [mailto:brian.le...@apihealthcare.com]
Sent: Monday, July 25, 2011 5:22 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Question on Patch Files.
When building a Patch for a setup should a patch file contain all items that
could change or just the ones I know that have changed. For example I have
the following defined:
PatchFamily Id=SoftwareUpdates Version=$(var.PublicVersion)
Supersede=yes ProductCode={----}
PropertyRef Id=ProductName/
ComponentRef Id=RegistrySettings /
ComponentRef Id=File1 /
ComponentRef Id=File2 /
ComponentRef Id=File3 /
/PatchFamily
The two setups I have only differ by one file, say File1. Should I only have
in the patch file the components that I know are different? Does it hurt to
put these other components in the patch file even if they don't change? I was
asking because would it make sense to perhaps have one patch file with
everything that could be patched listed in it so I don't have to create this
file over and over again?
--Brian
This message (including any attachments) contains confidential and privileged
information intended for a specific purpose, and is protected by law. If you
are not the intended recipient, you must delete this message and any
attachments. You are hereby notified that any disclosure, copying, or
distribution of this message, or any attachments, or the taking of any action
based on it, is strictly prohibited. Opinions, conclusions, and other
information in this message that do not relate to the official business of API
Healthcare Corporation (API Healthcare) shall be understood as neither given
nor endorsed by API Healthcare.
API Healthcare Corporation
1550 Innovation Way
Hartford, WI 53027
--
Storage Efficiency Calculator
This modeling tool is based on patent-pending intellectual property that has
been used successfully in hundreds of IBM storage optimization engage- ments,
worldwide. Store less, Store more with what you own, Move data to the right
place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are
intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged
information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
--
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question on Patch Files.
Actually, it's best if everything that might get patched gets authored into its
own fragment. If you patch whole fragments, pretty soon the MSP file is nearly
as big as the MSI--defeats the purpose.
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install Engineer - jXchange
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, July 26, 2011 4:14 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Question on Patch Files.
Normally a patch just includes resources that have changed, plus any changes
from earlier patches - Patch families can only grow.
As far as I know, when you refer to a resource in the patch family, the whole
fragment that the resource belongs to is pulled into the patch. Therefore you
could refer to just one thing in each fragment that you want in your list and
you'd not need to change it in future.
I would examine the resulting patch to see how much it has included - I don't
know if unchanged resources have any effect on the patch although I'd assume
not.
You'll likely have to edit your patch wxs every time to change the patch
display name, client patch ID etc although these could be automated.
-Original Message-
From: Brian Lemke [mailto:brian.le...@apihealthcare.com]
Sent: 25 July 2011 23:22
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Question on Patch Files.
When building a Patch for a setup should a patch file contain all items that
could change or just the ones I know that have changed. For example I have
the following defined:
PatchFamily Id=SoftwareUpdates Version=$(var.PublicVersion)
Supersede=yes ProductCode={----}
PropertyRef Id=ProductName/
ComponentRef Id=RegistrySettings /
ComponentRef Id=File1 /
ComponentRef Id=File2 /
ComponentRef Id=File3 /
/PatchFamily
The two setups I have only differ by one file, say File1. Should I only
have in the patch file the components that I know are different? Does it hurt
to put these other components in the patch file even if they don't change? I
was asking because would it make sense to perhaps have one patch file with
everything that could be patched listed in it so I don't have to create this
file over and over again?
--Brian
This message (including any attachments) contains confidential and privileged
information intended for a specific purpose, and is protected by law. If you
are not the intended recipient, you must delete this message and any
attachments. You are hereby notified that any disclosure, copying, or
distribution of this message, or any attachments, or the taking of any action
based on it, is strictly prohibited. Opinions, conclusions, and other
information in this message that do not relate to the official business of API
Healthcare Corporation (API Healthcare) shall be understood as neither given
nor endorsed by API Healthcare.
API Healthcare Corporation
1550 Innovation Way
Hartford, WI 53027
-
-
Storage Efficiency Calculator
This modeling tool is based on patent-pending intellectual property that has
been used successfully in hundreds of IBM storage optimization engage- ments,
worldwide. Store less, Store more with what you own, Move data to the right
place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and we
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY,
UK.
--
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are
intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged
information.
Any unauthorized review, use, printing, saving, copying,
Re: [WiX-users] Shortcuts question
Hi Phil, Thanks for your response. Do you recommend editing the record filed at runtime with the required value or creating a new record with the required value at runtime? Are there any issues with modifying a record field at runtime? When I call the MsiRecordSetString function, it returns ERROR_INVALID_HANDLE. I know that my view is valid - because MsiDatabaseOpenView returns success. So I am wondering if I should just create records or attempt to modify the existing record. Thanks! Uma- -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Monday, July 25, 2011 11:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Shortcuts question That works only when the corresponding field in the MSI is Formatted type. It may work if you update the in-memory MSI file with the required value prior to the CreateShortcuts action. I have no experience of doing this, but vaguely recall people using this technique. Phil Wilson -Original Message- From: Uma Harano [mailto:uhar...@esri.com] Sent: Monday, July 25, 2011 10:44 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Shortcuts question Hi, In the Shortcut table of the msi, I want to use a property (ST_NAME) for the Name column. The shortcut I am creating is shortcut to an IIS Virtual directory. The setup could change this location based on user input, so I want the shortcut name to reflect this change. I am finding that if I put [ST_NAME] in the Name column of the shortcut table, the msi creates a shortcut called [ST_NAME]. It doesn't resolve the property. Any ideas how I can solve this? Thanks! Uma- -- Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] com registration
I'm using heat to generate the fragment for my COM object. After installing the MSI, the CLSID entries are not created in the registry. Should I add Registry elements to my WXS file manually or am I doing something wrong? Thanks, Dariel -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Preventing a patch from installing.
Is it possible to prevent an update from applying to the system? I have a scenario where I have shipped v1.0 of my setup which has patches 1 and 2. After patch 2 is out but before the client can install it, they detect a critical error in patch 1 that requires us to immediately patch it (creating patch 3). Is there anything I can do that once patch 3 is installed to prevent patch 2 from installing since it may re-break the fix, especially if patch 2 edited the same files as patch 3. Or am I not understanding how patching is intended to work? (I come from a home grown setup system and trying to convert to use MSI\WiX.) --Brian This message (including any attachments) contains confidential and privileged information intended for a specific purpose, and is protected by law. If you are not the intended recipient, you must delete this message and any attachments. You are hereby notified that any disclosure, copying, or distribution of this message, or any attachments, or the taking of any action based on it, is strictly prohibited. Opinions, conclusions, and other information in this message that do not relate to the official business of API Healthcare Corporation (API Healthcare) shall be understood as neither given nor endorsed by API Healthcare. API Healthcare Corporation 1550 Innovation Way Hartford, WI 53027 -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Preventing a patch from installing.
See the attributes to the PatchFamily element; most specifically, the ProductCode, Supersede and Version attributes. -- John Merryweather Cooper Jack Henry Associates, Inc. (Premier Tech, Inc.) Build Install Engineer - jXchange Office: 913-341-3434 x791011 jocoo...@jackhenry.com -Original Message- From: Brian Lemke [mailto:brian.le...@apihealthcare.com] Sent: Tuesday, July 26, 2011 12:38 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Preventing a patch from installing. Is it possible to prevent an update from applying to the system? I have a scenario where I have shipped v1.0 of my setup which has patches 1 and 2. After patch 2 is out but before the client can install it, they detect a critical error in patch 1 that requires us to immediately patch it (creating patch 3). Is there anything I can do that once patch 3 is installed to prevent patch 2 from installing since it may re-break the fix, especially if patch 2 edited the same files as patch 3. Or am I not understanding how patching is intended to work? (I come from a home grown setup system and trying to convert to use MSI\WiX.) --Brian This message (including any attachments) contains confidential and privileged information intended for a specific purpose, and is protected by law. If you are not the intended recipient, you must delete this message and any attachments. You are hereby notified that any disclosure, copying, or distribution of this message, or any attachments, or the taking of any action based on it, is strictly prohibited. Opinions, conclusions, and other information in this message that do not relate to the official business of API Healthcare Corporation (API Healthcare) shall be understood as neither given nor endorsed by API Healthcare. API Healthcare Corporation 1550 Innovation Way Hartford, WI 53027 -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Primary Project Output
Hello, This is my first time using the mailing list, so please forgive any etiquette missteps. I currently use a Windows Installer project inside of VS2010 to create my final MSI package. One feature that I use there is that I can define Primary Output From .csproj in the File System, and this will use the references of the C# Project to grab all of the file dependencies. Likewise, there is a Content Files from .csproj that will include any files in the C# Project marked as Content. Is there an equivalent to this in WiX, or will I have to capture all of the dependencies manually? If I use heat.exe on the .csproj, will it capture the dependencies? Thank you, Joseph Tilley “This message and any attachments may contain FW Murphy information that is highly confidential, privileged, and exempt from disclosure. Any recipient other than the intended recipient is advised that dissemination, distribution, copying, or other use of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately, plus delete the message and any backups.” -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
