Re: [WiX-users] QFE authoring after service pack release
Thanks Peter and Chad!
I tried option 1. I may be interpreting this wrong, but I tried this
without sucess:
upgradeImage = newMSI (v.2002)
targetImage = rtmMSI (v.1000)
upgradeImage = newMSI (v.2002)
targetImage = sp1MSI (v.2000)
The error I get from msimsp.exe is: UpgradedImages.Upgraded = 'blah':
PackageCode {4E63E3D3-591B-4403-B0D2-8065687CCC61} is not unique.
I cannot find this GUID anywhere. 'blah' is Id the the second UpgradeImage I
specified.
Also, how do I find out more info about the validation bits?
Thanks!
Ning
On 10/10/07, Peter Marcu <[EMAIL PROTECTED]> wrote:
>
> The transforms in patches usually only apply to a single baseline. In
> your case, you chose your RTM as your baseline. A patch can carry multiple
> transforms but you will need to include both in the patch if you want your
> patch to apply to both scenarios.
>
>
>
> The other option is to carry the single transform and set the transform
> validation bits to say that the transform applies to 1.0.2000 and earlier.
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Chad Petersen
> *Sent:* Wednesday, October 10, 2007 9:26 AM
> *To:* Ning Lin; wix-users@lists.sourceforge.net
> *Subject:* Re: [WiX-users] QFE authoring after service pack release
>
>
>
> I believe the last digit of the version is ignored. You might have better
> luck using 1.0.2020 instead. Just a hunch. Might be worth a try.
>
>
> ------
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Ning Lin
> *Sent:* Wednesday, October 10, 2007 9:16 AM
> *To:* wix-users@lists.sourceforge.net
> *Subject:* Re: [WiX-users] QFE authoring after service pack release
>
>
>
> Resend ... Appreciate any pointers! Thanks!
>
>
>
> Ning
>
>
>
> Hello,
>
>
>
> So our scenario is this
>
> 1) Product RTM'ed (say version 1.0.1000)
>
> 2) We created and shipped a service pack 1 (say version 1.0.2000)
>
> 3) Now we realize we need to ship a QFE (say version 1.0.2002)
>
>
>
> So we created a QFE patch that is basically a diff between versions
> 1.0.1000 and versions 1.0.2002 -- it tries to update 1 file to version
> 1.0.2002.
>
>
>
> Now this QFE patch works on a machine that only has the RTM version
> installed, that 1 binary is updated to version 2002 as expected. On a
> machine that has SP1 installed, it simply does nothing! On the verbose log,
> it shows that it's trying to update the file to version 2000, since version
> 2000 is already on the machine, it does nothing.
>
>
>
> So my question is, should we author the QFE by diff'ing it to the RTM CD,
> or diff'ing it to the SP1 CD?
>
>
>
> Thank you for any input!
>
>
>
> Ning
>
>
>
>
>
>
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] QFE authoring after service pack release
Resend ... Appreciate any pointers! Thanks! Ning > Hello, > > So our scenario is this > 1) Product RTM'ed (say version 1.0.1000) > 2) We created and shipped a service pack 1 (say version 1.0.2000) > 3) Now we realize we need to ship a QFE (say version 1.0.2002) > > So we created a QFE patch that is basically a diff between versions > 1.0.1000 and versions 1.0.2002 -- it tries to update 1 file to version > 1.0.2002. > > Now this QFE patch works on a machine that only has the RTM version > installed, that 1 binary is updated to version 2002 as expected. On a > machine that has SP1 installed, it simply does nothing! On the verbose log, > it shows that it's trying to update the file to version 2000, since version > 2000 is already on the machine, it does nothing. > > So my question is, should we author the QFE by diff'ing it to the RTM CD, > or diff'ing it to the SP1 CD? > > Thank you for any input! > > Ning > > > - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] QFE authoring after service pack release
Hello, So our scenario is this 1) Product RTM'ed (say version 1.0.1000) 2) We created and shipped a service pack 1 (say version 1.0.2000) 3) Now we realize we need to ship a QFE (say version 1.0.2002) So we created a QFE patch that is basically a diff between versions 1.0.1000and versions 1.0.2002 -- it tries to update 1 file to version 1.0.2002. Now this QFE patch works on a machine that only has the RTM version installed, that 1 binary is updated to version 2002 as expected. On a machine that has SP1 installed, it simply does nothing! On the verbose log, it shows that it's trying to update the file to version 2000, since version 2000 is already on the machine, it does nothing. So my question is, should we author the QFE by diff'ing it to the RTM CD, or diff'ing it to the SP1 CD? Thank you for any input! Ning - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixUI library support for 3.0
Thanks for your help! It has resolved my problem now.
Ning
On 2/3/07, Mike Dimmick <[EMAIL PROTECTED]> wrote:
Just a nitpicking correction: .wixlib files _are_ still supported.
However,
extension DLLs can now carry an embedded .wixlib, and this feature has
been
used for most of the WiX extended features (i.e. anything beyond what
Windows Installer itself provides). Therefore, tasks that required you to
provide one of the standard .wixlib files in 2.0 now require you to
specify
the appropriate extension to light.exe.
This doesn't stop you compiling your own .wixlib files if you have common
components you want to reuse in many packages.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] ] On Behalf Of Jeff Bean
Sent: 03 February 2007 06:45
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WixUI library support for 3.0
The wixlib libraries are dlls now. Here is what I did:
candle -out obj\MyInstall.wixobj -ext WixUIExtension MyInstall.wxs
light -cultures:en-us -ext WixUIExtension -loc MyInstall.wxl -out
MyInstall.msi obj\MyInstall.wixobj
where MyInstall.wxs contains (amongst other stuff):
You would change the WixUI_InstallDir to WixUI_Minimal if that is the UI
set
you want. You also wouldn't need the WIXUI_INSTALLDIR property in that
case.
MyInstall.wxl contains an override of one of the messages in the user
interface:
http://schemas.microsoft.com/wix/2006/localization";>
{\WixUI_Font_Normal} will be installed to
[TARGETDIR]
Click Install to begin the installation.
Click Back to review or change any of your settings.
Click Cancel to exit the wizard.
Ning Lin wrote:
>
> According to this page, .wixlib is no longer supported:
> http://sourceforge.net/mailarchive/message.php?msg_id=36313215
>
> I am in need of just a minimal UI as provided by the wix ui library from
> 2.0.
> What is the story here for 3.0? I tried to use the 2.0 library with
> no success, especially also because I needed to link with a .wixout
> object.
>
> Thanks for any pointers!
>
> Ning
>
>
--
View this message in context:
http://www.nabble.com/WixUI-library-support-for-3.0-tf3164519.html#a8779936
Sent from the wix-users mailing list archive at Nabble.com<http://nabble.com/>
.
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixUI library support for 3.0
According to this page, .wixlib is no longer supported: http://sourceforge.net/mailarchive/message.php?msg_id=36313215 I am in need of just a minimal UI as provided by the wix ui library from 2.0. What is the story here for 3.0? I tried to use the 2.0 library with no success, especially also because I needed to link with a .wixout object. Thanks for any pointers! Ning - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
