Re: [WiX-users] Windows updates
On 12/07/2013 10:56, Pally Sandher wrote: > Question is if these machines don't have internet access, why is keeping them > up to date an issue? One problem with machines that don't have Internet access is that installers which are Authenticode-signed won't install unless the root certificate has already been installed - Windows tries to automatically download it. On a plain Server 2008 machine for example installation fails if it has never been connected to the Internet because the signature can't be verified. -- Bruce Cran -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Win8.1 + DIFx problem...
Have you filed a bug report with Microsoft? -- Bruce Cran Sent from my iPhone On 16 Jul 2013, at 13:27, "Gonzalez, John" wrote: > I have the same, or similar, issue. It is not expected and showed up around > the 9419 build release. Currently have no ETA of a fix. > > Thanks, > John > > > -Original Message- > From: Robert Randall [mailto:robert.r.rand...@gmail.com] > Sent: Tuesday, July 16, 2013 12:03 PM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Win8.1 + DIFx problem... > > I have a device driver install which is working just fine. However, I'm > getting different behavior on Win8.1 compared to the previous releases of > Windows (Vista, Win7, Win8). > > On the previous releases of Windows, removing the MSI package from the > Control Panel->Programs and Features results in the device driver being > removed from the driver store. It also results in the replacement of the > active drivers instances with the nul device driver. I don't know if this is > default DIFx behavior or something that WiX is asking DIFx to do for me. > > On Win8.1, the driver package is removed from the driver store but the driver > instances are not being changed in any way. > > Is this expected behavior? > > I'll do some digging and see if DIFx is installing the nul driver based on > the DIFx action or if WiX is doing it just to be kind (and yes, it is kind of > WiX). > > Best regards, > Robert. > > -- > Robert Randall | robert.r.rand...@gmail.com > -- > See everything from the browser to the database with AppDynamics Get > end-to-end visibility with application monitoring from AppDynamics Isolate > bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn uninstalls product instead of upgrading it
I seem to have managed to get Burn rather confused. I have an MSI
package with new product and upgrade codes in version 2.0 due to
different builds being produced. I ask Windows Installer (in the MSI) to
upgrade from the previous one with:
Snippet
NOT OTHER_PRODUCT_INSTALLED
However, when I run the installer, Burn logs:
Detected related bundle: {BUNDLE_GUID}, type: Upgrade, scope:
PerMachine, version: 1.0.0, operation: MajorUpgrade
Detected related package: {OLD_PRODUCT_CODE}, scope: PerMachine,
version: 1.0.0, language: 0 operation: MajorUpgrade
Detected related package: {OLD_PRODUCT_CODE}, scope: PerMachine,
version: 1.0.0, language: 0 operation: Downgrade
Detected package: Product.msi, state: Obsolete, cached: None
...
Planned package: Product.msi, state: Obsolete, default requested: None,
ba requested: None, execute: None, rollback: None, cache: No, uncache:
No, dependency: None
Planned related bundle: {BUNDLE_GUID}, type: Upgrade, default requested:
Absent, ba requested: Absent, execute: Uninstall, rollback: Install,
dependency: None
...
It then proceeeds to uninstall the product but leave the new version in
Add/Remove Programs.
Any idea what I'm doing wrong?
--
Bruce Cran
--
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [Wix]: Create silent MSI using Wix
On 23/08/2013 15:20, Alain Forget wrote: > Don't WiX-built MSIs have no UI by default? > > See the second paragraph of > http://wix.tramontana.co.hu/tutorial/user-interface > > So just follow the steps of the Getting Started tutorial, and don't do > anything in the UI section? I think there's a single noninteractive dialog that pops up that I suspect you can't avoid other than by using /quiet. -- Bruce -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn uninstalls product instead of upgrading it
On 23/08/2013 21:58, Rob Mensching wrote: > Might be related to: http://wixtoolset.org/issues/3643/ Thanks, that was the problem. -- Bruce -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn, signature verification and failure on Vista
I recently discovered the certificate auto-download feature in Vista/2008 when I found that our installer (which uses Burn) fails due to an authenticode verification error when the machine isn't connected to the Internet. It seems that when Burn asks Windows to check the signature, if the root certificate is missing (which it will be if it's not been asked to check before) Windows downloads it from Microsoft. If it can't, verification fails and so does the installation. What I'm wondering is if this is only something likely to happen on test systems - in production is there some other way Windows is likely to have the updated certificates? Or, should I remove the signature on the installer and MSI file to avoid this problem? Or is there a way to ask Burn to skip the verification step? -- Bruce Cran -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
On 28/08/2013 06:07, Blair Murri wrote: > As I understand it, page "Success" will be shown whenever the result of > bundle application is successful but not when a failure occurs (when instead > the "Failure" page will be shown). So, successful install, successful > removal, successful modification, etc. > If you can set bundle properties you can use that property's value as your > text, maybe... There was a discussion on wix-devs about this a few months ago: the WixStdBA bootstrapper needs changed to allow better text on the 'success' pages. In particular, people have complained to me about the fact that when uninstall completes it reports "Setup Success". -- Bruce Cran -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
Could you sent a pull request to integrate this change upstream please?
--
Bruce Cran
Sent from my iPhone
On 28 Aug 2013, at 14:28, Steven Ogilvie wrote:
> Yes exactly
>
> BA is using the same property for Setup/Uninstall for the success/failure
> string
>
> I fixed this by changing the code in BA and adding a few extra string
> properties in the theme wxl file
> Setup Successful
> Setup Successful
> Uninstall Successful
> Setup Failed
> Setup Failed
> Uninstall Failed
>
> BA:
>
> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>{ WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>{ WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER, L"SuccessUninstallHeader" },
>
> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>{ WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>{ WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER, L"FailureUninstallHeader" },
>
> The in OnChangeState is where I set the correct string
>
>
> -Original Message-
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: August-28-13 2:26 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add text to final window in burn
> bootstrapper/installer
>
> On 28/08/2013 06:07, Blair Murri wrote:
>> As I understand it, page "Success" will be shown whenever the result of
>> bundle application is successful but not when a failure occurs (when instead
>> the "Failure" page will be shown). So, successful install, successful
>> removal, successful modification, etc.
>> If you can set bundle properties you can use that property's value as your
>> text, maybe...
>
> There was a discussion on wix-devs about this a few months ago: the WixStdBA
> bootstrapper needs changed to allow better text on the 'success' pages. In
> particular, people have complained to me about the fact that when uninstall
> completes it reports "Setup Success".
>
> --
> Bruce Cran
>
> --
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Discover the easy way to master current and previous Microsoft technologies
> and advance your career. Get an incredible 1,500+ hours of step-by-step
> tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Discover the easy way to master current and previous Microsoft technologies
> and advance your career. Get an incredible 1,500+ hours of step-by-step
> tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
Yes that was for Steven: he's made exactly the same changes I was hoping to get
around to making, and I'd like to see them get into WiX 3.8 if possible.
--
Bruce
Sent from my iPhone
On 28 Aug 2013, at 16:52, "Alain Forget" wrote:
> I hope that's directed at Steven, because I don't know what that means (and I
> have yet to figure out where and how to modify .wxl files).
>
> Alain
>
> -Original Message-
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: Wednesday, August 28, 2013 11:39 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add text to final window in burn
> bootstrapper/installer
>
> Could you sent a pull request to integrate this change upstream please?
>
> --
> Bruce Cran
>
> Sent from my iPhone
>
> On 28 Aug 2013, at 14:28, Steven Ogilvie wrote:
>
>> Yes exactly
>>
>> BA is using the same property for Setup/Uninstall for the success/failure
>> string
>>
>> I fixed this by changing the code in BA and adding a few extra string
>> properties in the theme wxl file
>> Setup Successful
>> Setup Successful
>> Uninstall Successful
>> Setup Failed
>> Setup Failed
>> Uninstall Failed
>>
>> BA:
>>
>> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>> { WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>> { WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER, L"SuccessUninstallHeader" },
>>
>> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>> { WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>> { WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER, L"FailureUninstallHeader" },
>>
>> The in OnChangeState is where I set the correct string
>>
>>
>> -Original Message-
>> From: Bruce Cran [mailto:br...@cran.org.uk]
>> Sent: August-28-13 2:26 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Add text to final window in burn
>> bootstrapper/installer
>>
>> On 28/08/2013 06:07, Blair Murri wrote:
>>> As I understand it, page "Success" will be shown whenever the result of
>>> bundle application is successful but not when a failure occurs (when
>>> instead the "Failure" page will be shown). So, successful install,
>>> successful removal, successful modification, etc.
>>> If you can set bundle properties you can use that property's value as your
>>> text, maybe...
>>
>> There was a discussion on wix-devs about this a few months ago: the WixStdBA
>> bootstrapper needs changed to allow better text on the 'success' pages. In
>> particular, people have complained to me about the fact that when uninstall
>> completes it reports "Setup Success".
>>
>> --
>> Bruce Cran
>>
>> --
>> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
>> Discover the easy way to master current and previous Microsoft technologies
>> and advance your career. Get an incredible 1,500+ hours of step-by-step
>> tutorial videos with LearnDevNow. Subscribe today and save!
>> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>> --
>> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
>> Discover the easy way to master current and previous Microsoft technologies
>> and advance your career. Get an incredible 1,500+ hours of step-by-step
>> tutorial videos with LearnDevNow. Subscribe today and save!
>> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Discover the easy way to master current and previous Microsoft technologies
> and advance your career. Get an incredible 1,500+ hours of step-by-step
> tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.double
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
Okay, I can submit it.
--
Bruce
Sent from my iPhone
On 28 Aug 2013, at 18:13, Steven Ogilvie wrote:
> You want me to make the change for 3.8 or your going to make the change?
>
> I can send you my code for the BA if you want :)
>
> -Original Message-
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: August-28-13 12:34 PM
> To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add text to final window in burn
> bootstrapper/installer
>
> Yes that was for Steven: he's made exactly the same changes I was hoping to
> get around to making, and I'd like to see them get into WiX 3.8 if possible.
>
> --
> Bruce
>
> Sent from my iPhone
>
> On 28 Aug 2013, at 16:52, "Alain Forget" wrote:
>
>> I hope that's directed at Steven, because I don't know what that means (and
>> I have yet to figure out where and how to modify .wxl files).
>>
>> Alain
>>
>> -Original Message-
>> From: Bruce Cran [mailto:br...@cran.org.uk]
>> Sent: Wednesday, August 28, 2013 11:39 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Add text to final window in burn
>> bootstrapper/installer
>>
>> Could you sent a pull request to integrate this change upstream please?
>>
>> --
>> Bruce Cran
>>
>> Sent from my iPhone
>>
>> On 28 Aug 2013, at 14:28, Steven Ogilvie wrote:
>>
>>> Yes exactly
>>>
>>> BA is using the same property for Setup/Uninstall for the
>>> success/failure string
>>>
>>> I fixed this by changing the code in BA and adding a few extra string
>>> properties in the theme wxl file Setup
>>> Successful Setup
>>> Successful Uninstall
>>> Successful Setup Failed
>>> Setup Failed >> Id="FailureUninstallHeader">Uninstall Failed
>>>
>>> BA:
>>>
>>> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>> L"SuccessUninstallHeader" },
>>>
>>> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>> L"FailureUninstallHeader" },
>>>
>>> The in OnChangeState is where I set the correct string
>>>
>>>
>>> -Original Message-
>>> From: Bruce Cran [mailto:br...@cran.org.uk]
>>> Sent: August-28-13 2:26 AM
>>> To: General discussion for Windows Installer XML toolset.
>>> Subject: Re: [WiX-users] Add text to final window in burn
>>> bootstrapper/installer
>>>
>>> On 28/08/2013 06:07, Blair Murri wrote:
>>>> As I understand it, page "Success" will be shown whenever the result of
>>>> bundle application is successful but not when a failure occurs (when
>>>> instead the "Failure" page will be shown). So, successful install,
>>>> successful removal, successful modification, etc.
>>>> If you can set bundle properties you can use that property's value as your
>>>> text, maybe...
>>>
>>> There was a discussion on wix-devs about this a few months ago: the
>>> WixStdBA bootstrapper needs changed to allow better text on the 'success'
>>> pages. In particular, people have complained to me about the fact that
>>> when uninstall completes it reports "Setup Success".
>>>
>>> --
>>> Bruce Cran
>>>
>>> -
>>> - Learn the latest--Visual Studio 2012, SharePoint 2013, SQL
>>> 2012, more!
>>> Discover the easy way to master current and previous Microsoft technologies
>>> and advance your career. Get an incredible 1,500+ hours of step-by-step
>>> tutorial videos with LearnDevNow. Subscribe today and save!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.
>>> clktrk ___
>>> WiX-users mailing list
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>> -
>>> - Lea
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
I'll submit the pull request tomorrow: it'll then be up to Bob to decide
if/when it gets committed.
--
Bruce
Sent from my iPhone
On 28 Aug 2013, at 19:14, "Alain Forget" wrote:
> Will this functionality be available on Monday (or sooner) at
> http://wixtoolset.org/releases/ ?
>
> If so, how will I be able to add text to the Setup Complete box? My apologies
> if I seem a tad dense, but this is very unfamiliar territory for me.
>
> -Original Message-
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: Wednesday, August 28, 2013 2:02 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add text to final window in burn
> bootstrapper/installer
>
> Okay, I can submit it.
>
> --
> Bruce
>
> Sent from my iPhone
>
> On 28 Aug 2013, at 18:13, Steven Ogilvie wrote:
>
>> You want me to make the change for 3.8 or your going to make the change?
>>
>> I can send you my code for the BA if you want :)
>>
>> -Original Message-
>> From: Bruce Cran [mailto:br...@cran.org.uk]
>> Sent: August-28-13 12:34 PM
>> To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Add text to final window in burn
>> bootstrapper/installer
>>
>> Yes that was for Steven: he's made exactly the same changes I was hoping to
>> get around to making, and I'd like to see them get into WiX 3.8 if possible.
>>
>> --
>> Bruce
>>
>> Sent from my iPhone
>>
>> On 28 Aug 2013, at 16:52, "Alain Forget" wrote:
>>
>>> I hope that's directed at Steven, because I don't know what that means (and
>>> I have yet to figure out where and how to modify .wxl files).
>>>
>>> Alain
>>>
>>> -Original Message-
>>> From: Bruce Cran [mailto:br...@cran.org.uk]
>>> Sent: Wednesday, August 28, 2013 11:39 AM
>>> To: General discussion for Windows Installer XML toolset.
>>> Subject: Re: [WiX-users] Add text to final window in burn
>>> bootstrapper/installer
>>>
>>> Could you sent a pull request to integrate this change upstream please?
>>>
>>> --
>>> Bruce Cran
>>>
>>> Sent from my iPhone
>>>
>>> On 28 Aug 2013, at 14:28, Steven Ogilvie wrote:
>>>
>>>> Yes exactly
>>>>
>>>> BA is using the same property for Setup/Uninstall for the
>>>> success/failure string
>>>>
>>>> I fixed this by changing the code in BA and adding a few extra string
>>>> properties in the theme wxl file Setup
>>>> Successful Setup
>>>> Successful Uninstall
>>>> Successful Setup Failed
>>>> Setup Failed >>> Id="FailureUninstallHeader">Uninstall Failed
>>>>
>>>> BA:
>>>>
>>>> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>>>> { WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>>>> { WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>>> L"SuccessUninstallHeader" },
>>>>
>>>> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>>>> { WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>>>> { WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>>> L"FailureUninstallHeader" },
>>>>
>>>> The in OnChangeState is where I set the correct string
>>>>
>>>>
>>>> -Original Message-
>>>> From: Bruce Cran [mailto:br...@cran.org.uk]
>>>> Sent: August-28-13 2:26 AM
>>>> To: General discussion for Windows Installer XML toolset.
>>>> Subject: Re: [WiX-users] Add text to final window in burn
>>>> bootstrapper/installer
>>>>
>>>> On 28/08/2013 06:07, Blair Murri wrote:
>>>>> As I understand it, page "Success" will be shown whenever the result of
>>>>> bundle application is successful but not when a failure occurs (when
>>>>> instead the "Failure" page will be shown). So, successful install,
>>>>> successful removal, successful modification, etc.
>>>>> If you can set bundle properties you can use that property's value as
>>>>> your text, maybe...
>>>>
>>>> There was a discussion on wix-devs about this a few months ago: the
>>>> WixStdBA bootstrapper needs changed
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
Do you have a diff (e.g. using 'git diff') you can attach?
--
Bruce
Sent from my iPhone
On 28 Aug 2013, at 18:29, Steven Ogilvie wrote:
> Here is the code from BA
>
> Theme wxl file
> Setup Successful
> Setup Successful
> Uninstall Successful
>
> Setup Failed
> Setup Failed
> Uninstall Failed
>
> Theme xml file
>
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.SuccessHeader)
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.SuccessSetupHeader)
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.SuccessUninstallHeader)
>
>
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.FailureHeader)
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.FailureSetupHeader)
> FontId="2" HideWhenDisabled="yes"
> DisablePrefix="yes">#(loc.FailureUninstallHeader)
>
> WixStandardBootstrapperApplication.cpp
>
> // Success page
>WIXSTDBA_CONTROL_SUCCESS_HEADER,
>WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER,
>WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>
> // Failure page
>WIXSTDBA_CONTROL_FAILURE_HEADER,
>WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER,
>WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>
> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>{ WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>{ WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER, L"SuccessUninstallHeader" },
>
> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>{ WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>{ WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER, L"FailureUninstallHeader" },
>
> In method OnChangeState:
> ..
> else if (m_rgdwPageIds[WIXSTDBA_PAGE_SUCCESS] == dwNewPageId) // on the
> "Success" page, check if the restart or launch button should be enabled.
> ...
> // Set the header of the failure page to either Setup or Uninstall
>if (ThemeControlExists(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER))
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, BOOTSTRAPPER_ACTION_UNINSTALL <
> m_plannedAction);
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_HEADER, FALSE);
>}
>else
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_HEADER, TRUE);
>}
>if (ThemeControlExists(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER))
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER, BOOTSTRAPPER_ACTION_INSTALL >
> m_plannedAction);
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_HEADER, FALSE);
>}
>else
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_SUCCESS_HEADER, TRUE);
>}
> ...
> else if (m_rgdwPageIds[WIXSTDBA_PAGE_FAILURE] == dwNewPageId) // on the
> "Failure" page, show error message and check if the restart button should be
> enabled.
> ...
> // Set the header of the failure page to either Setup or Uninstall
>if (ThemeControlExists(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER))
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, BOOTSTRAPPER_ACTION_UNINSTALL <
> m_plannedAction);
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_HEADER, FALSE);
>}
>else
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_HEADER, TRUE);
>}
>if (ThemeControlExists(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER))
>{
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER, BOOTSTRAPPER_ACTION_INSTALL >
> m_plannedAction);
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_FAILURE_HEADER, FALSE);
>}
>else
> {
>ThemeControlEnable(m_pTheme,
> WIXSTDBA_CONTROL_
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
I'm working on a patch against 3.8 that I hope to put on codeplex later today.
--
Bruce
Sent from my iPhone
On 31 Aug 2013, at 10:02, Neil Sleightholm wrote:
> If you like to post diff on the code plea site I'll add it to the extended
> BA.
>
> Neil
>
> On 30 Aug 2013, at 14:48, "Steven Ogilvie" wrote:
>
>> No sorry
>>
>> I am not using 3.8 I am using 3.7 with the Extended BA from Neil
>>
>> -Original Message-
>> From: Bruce Cran [mailto:br...@cran.org.uk]
>> Sent: August-30-13 9:00 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Add text to final window in burn
>> bootstrapper/installer
>>
>> Do you have a diff (e.g. using 'git diff') you can attach?
>>
>> --
>> Bruce
>>
>> Sent from my iPhone
>>
>> On 28 Aug 2013, at 18:29, Steven Ogilvie wrote:
>>
>>> Here is the code from BA
>>>
>>> Theme wxl file
>>> Setup Successful >> Id="SuccessSetupHeader">Setup Successful >> Id="SuccessUninstallHeader">Uninstall Successful
>>>
>>> Setup Failed >> Id="FailureSetupHeader">Setup Failed >> Id="FailureUninstallHeader">Uninstall Failed
>>>
>>> Theme xml file
>>>
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessHeader)
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessSetupHeader)
>>> >> Height="30" FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessUninstallHeader)
>>>
>>>
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureHeader)
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureSetupHeader)
>>> >> Height="30" FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureUninstallHeader)
>>>
>>> WixStandardBootstrapperApplication.cpp
>>>
>>> // Success page
>>> WIXSTDBA_CONTROL_SUCCESS_HEADER,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER,
>>> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>>
>>> // Failure page
>>> WIXSTDBA_CONTROL_FAILURE_HEADER,
>>> WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER,
>>> WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>>
>>> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>> L"SuccessUninstallHeader" },
>>>
>>> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>> L"FailureUninstallHeader" },
>>>
>>> In method OnChangeState:
>>> ..
>>> else if (m_rgdwPageIds[WIXSTDBA_PAGE_SUCCESS] == dwNewPageId) // on the
>>> "Success" page, check if the restart or launch button should be enabled.
>>> ...
>>> // Set the header of the failure page to either Setup or Uninstall
>>> if (ThemeControlExists(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER))
>>> {
>>> ThemeControlEnable(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, BOOTSTRAPPER_ACTION_UNINSTALL <
>>> m_plannedAction);
>>> ThemeControlEnable(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_HEADER, FALSE);
>>> }
>>> else
>>> {
>>> ThemeControlEnable(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_HEADER, TRUE);
>>> }
>>> if (ThemeControlExists(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER))
>>> {
>>> ThemeControlEnable(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER, BOOTSTRAPPER_ACTION_INSTALL >
>>> m_plannedAction);
>>> ThemeControlEnable(m_pTheme,
>>>
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
Can't Steven put the change in the public domain and someone who's already signed the agreement can commit it? -- Bruce Sent from my iPhone On 31 Aug 2013, at 04:10, Bob Arnson wrote: > On 28-Aug-13 13:29, Steven Ogilvie wrote: >> > FontId="2" HideWhenDisabled="yes" >> DisablePrefix="yes">#(loc.SuccessHeader) >> > FontId="2" HideWhenDisabled="yes" >> DisablePrefix="yes">#(loc.SuccessSetupHeader) >> > Height="30" FontId="2" HideWhenDisabled="yes" >> DisablePrefix="yes">#(loc.SuccessUninstallHeader) > Why separate controls? ThemeSetTextControl could be used with the > appropriate loc string. Also, differentiating uninstall is fine but > certainly other actions should get the same treatment, no? > > Logistics: You'd have to sign an assignment agreement since you're the > one providing the change. > > -- > sig://boB > http://joyofsetup.com/ > > > -- > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
On 30/08/2013 14:46, Steven Ogilvie wrote: > No sorry > > I am not using 3.8 I am using 3.7 with the Extended BA from Neil Steven, I can't commit your code due to copyright issues, so would you be willing to sign the WiX copyright assignment agreement and upload the code to wix.codeplex.com yourself? -- Bruce Cran -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
That's another feature I'm hoping to implement: Burn should support 'Modifying'
the installation, displaying the options page during maintenance.
--
Bruce
Sent from my iPhone
On 16 Sep 2013, at 15:59, Steven Ogilvie wrote:
> Did I send you updated code?
>
> Different question...
>
> If I have two check boxes, each one a different installer, if I install one,
> how can I run the boostrapper again and choose to install the other?
> Currently it installs the 1 I have checked, run bootstrapper again and it
> wants to uninstall :(
>
> Steve
>
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: August-31-13 5:02 AM
> To: General discussion for Windows Installer XML toolset.
> Cc: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add text to final window in burn
> bootstrapper/installer
>
> If you like to post diff on the code plea site I'll add it to the extended
> BA.
>
> Neil
>
> On 30 Aug 2013, at 14:48, "Steven Ogilvie" wrote:
>
>> No sorry
>>
>> I am not using 3.8 I am using 3.7 with the Extended BA from Neil
>>
>> -Original Message-
>> From: Bruce Cran [mailto:br...@cran.org.uk]
>> Sent: August-30-13 9:00 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Add text to final window in burn
>> bootstrapper/installer
>>
>> Do you have a diff (e.g. using 'git diff') you can attach?
>>
>> --
>> Bruce
>>
>> Sent from my iPhone
>>
>> On 28 Aug 2013, at 18:29, Steven Ogilvie wrote:
>>
>>> Here is the code from BA
>>>
>>> Theme wxl file
>>> Setup Successful >> Id="SuccessSetupHeader">Setup Successful >> Id="SuccessUninstallHeader">Uninstall Successful
>>>
>>> Setup Failed >> Id="FailureSetupHeader">Setup Failed >> Id="FailureUninstallHeader">Uninstall Failed
>>>
>>> Theme xml file
>>>
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessHeader)
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessSetupHeader)
>>> >> Height="30" FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.SuccessUninstallHeader)
>>>
>>>
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureHeader)
>>> >> FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureSetupHeader)
>>> >> Height="30" FontId="2" HideWhenDisabled="yes"
>>> DisablePrefix="yes">#(loc.FailureUninstallHeader)
>>>
>>> WixStandardBootstrapperApplication.cpp
>>>
>>> // Success page
>>> WIXSTDBA_CONTROL_SUCCESS_HEADER,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER,
>>> WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>>
>>> // Failure page
>>> WIXSTDBA_CONTROL_FAILURE_HEADER,
>>> WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER,
>>> WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>>
>>> { WIXSTDBA_CONTROL_SUCCESS_HEADER, L"SuccessHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, L"SuccessSetupHeader" },
>>> { WIXSTDBA_CONTROL_SUCCESS_UNINSTALL_HEADER,
>>> L"SuccessUninstallHeader" },
>>>
>>> { WIXSTDBA_CONTROL_FAILURE_HEADER, L"FailureHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_SETUP_HEADER, L"FailureSetupHeader" },
>>> { WIXSTDBA_CONTROL_FAILURE_UNINSTALL_HEADER,
>>> L"FailureUninstallHeader" },
>>>
>>> In method OnChangeState:
>>> ..
>>> else if (m_rgdwPageIds[WIXSTDBA_PAGE_SUCCESS] == dwNewPageId) // on the
>>> "Success" page, check if the restart or launch button should be enabled.
>>> ...
>>> // Set the header of the failure page to either Setup or Uninstall
>>> if (ThemeControlExists(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER))
>>> {
>>> ThemeControlEnable(m_pTheme,
>>> WIXSTDBA_CONTROL_SUCCESS_SETUP_HEADER, BOOTSTRAPPER_ACTION_UNINSTALL <
>>> m_plannedAction);
>>>
Re: [WiX-users] Add text to final window in burn bootstrapper/installer
On 18/09/2013 14:08, Steven Ogilvie wrote: > So it is not currently supported? I don't think so. At least, the WixStdBA doesn't. -- Bruce Cran -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] install only on server 2012 and server 2008
On 9/20/2013 12:20 PM, nkshirsagar wrote: > I need to be able to install only on windows server 2012 and windows server > 2008 r2, everything else is a no-no.. (no client OS, no vista, no xp, no > windows 7/8) what condition should I use? See http://msdn.microsoft.com/en-us/library/windows/desktop/aa370905%28v=vs.85%29.aspx#operating_system_properties You'll probably want VersionNT >= 6.1 And VersionNT < 6.3 And MsiNTProductType > 1 With Windows Server 2012 R2 now released to MSDN you might want to drop the "VersionNT < 6.3" condition if you want to support it and future versions of Windows (2008R2 is 6.1, 2012 is 6.2, 2012 R2 is 6.3). -- Bruce Cran -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] install only on server 2012 and server 2008
On 9/23/2013 5:23 AM, Steven Ogilvie wrote: > Check out VersionNT and NTProductType (Google them to get the proper values > for the two OS's you want) Or read my reply :) -- Bruce Cran -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wixtoolset.org reporting 503 - service unavailable
http://wixtoolset.org/ reports: Service Unavailable HTTP Error 503. The service is unavailable. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Howto override variables from a file using MSBuild/VS2012
On 10/8/2013 1:03 AM, Blair Murri wrote: > The rest (of us) buy the book > (http://www.amazon.com/gp/product/0735626286?ie=UTF8&tag=sedodream-20&linkCode=xm2&camp=1789&creativeASIN=0735626286) Note that the link is for the first edition, not the second. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wixtoolset.org weekly builds downloads missing (404)
None of the builds via wixtoolset.org are working. For example trying to download 3.8.1007 results in the broken link http://wixtoolset.org/downloads/v3.8.1007.0/wix38.exe. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wixtoolset.org weekly builds downloads missing (404)
On 10/11/2013 5:42 PM, Bruce Cran wrote: > None of the builds via wixtoolset.org are working. For example trying > to download 3.8.1007 results in the broken link > http://wixtoolset.org/downloads/v3.8.1007.0/wix38.exe. > After refreshing each page it now works. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing binaries and msi...
On 10/22/2013 3:00 PM, Tony wrote: > > > To avoid the signature going invalid when the certificate expires, you probably want to add a timestamp: http://timestamp.verisign.com/scripts/timstamp.dll /> (that isn't a typo - "timstamp.dll" is 8.3 format). If you have a Globalsign cert, you might want to use timestamp.globalsign.com instead etc. And for the MSI file, you might want to add: /n text-that-should-appear-in-UAC-elevation-prompt-description Otherwise, the description will contain a randomly-generated filename. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing binaries and msi...
On 10/22/2013 6:47 PM, Tony wrote: > Answering my own question... > > ".(though now I see it needs to be "property", so I'll give that a try)" > <-- that was it. I don't know why I was thinking it need to be a WiX > property and/or preprocessor variable. **OBVIOUSLY** it needs to be a > "property" within the project file. Duh! > > Now the signing attempt fails as expected. I'll go grab our signing cert > and give it try. When you install the cert you might want to change the signtool commands to specify its thumbprint instead of relying on signtool's auto-selection: signtool sign /sha1 cert-thumbprint or, specify the cert's Subject Name with /n. I realised my previous email used the wrong parameter for the description: I think it's actually /d. Another thing: MSBuild has a built-in task for running signtool, SignFile - http://msdn.microsoft.com/en-us/library/ms164304.aspx. But I ended up writing my own implementation which retries 10 times with pauses in-between to try and handle network problems which prevent the timestamp server being reached. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing binaries and msi...
On 10/23/2013 2:13 AM, darren.benn...@listech.com wrote: > I'm interested to know how you went about implementing > your own task for code signing? I wrote an inline task in C# that shells out to signtool.exe with retries. It has thumbprint, crosscertificate, timestamp, retries and signingtargets parameters. -- Bruce Cran -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] repair does not repair file that was changed
On 10/28/2013 1:35 PM, Andrew Makhorin wrote: > Is there any way to tell the installer to always install original files > provided in .msi on repairing/reinstalling the product? See http://technet.microsoft.com/en-us/library/cc759262%28v=ws.10%29.aspx?ppud=4#BKMK_Repair . -- Bruce -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: [SPAM] Re: Errors installing 3.7
On 9/25/2013 2:47 PM, keith.doug...@statcan.gc.ca wrote: > Hi everyone, I thought I'd update the answer to my question from last week: > > For what it is worth, our server support team found KB931125, which seems to > have been the correct one for Server 2003 R2 Enterprise. By the way don't install KB931125 on Windows Server 2008 or newer - it's only designed for XP/2003 and client builds (i.e. XP, Server2003, Vista, Win7, Win8, Win8.1). See http://blogs.technet.com/b/windowsserver/archive/2013/01/12/fix-available-for-root-certificate-update-issue-on-windows-server.aspx for details of what can go wrong. You're supposed to import just the specific certificates you need from another machine. -- Bruce Cran -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom action was working now it isn't.... HELP...
On 10/31/2013 7:50 PM, Steven Ogilvie wrote: > So weird... > > Was working before, stopped working... function name had 26 characters > removed 7 characters now it works... Something we discussed today was how the CA log name when calling WcaInitialize() has a maximum of 32 characters - anything more than that and it fails with an "Insufficient buffer" error. Could something similar be happening? -- Bruce Cran -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Microsoft Reciprocal License explaination
On 11/20/2013 8:52 AM, John Ludlow wrote: > The only reason I can see not to do this is because it depends on > proprietary code, which either has no use outside your environment, or is > considered part of your own product and can't be distributed. Or if you think the changes are so awesome you want to prevent your competitors from getting the improvements :) -- Bruce Cran -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing all DLLs and EXEs in project
I guess the OP is talking about native binaries, not .NET assemblies
since he mentioned signtool - sn is the .NET signing tool.
--
Bruce
On 12/18/2013 1:23 PM, John Cooper wrote:
> You'll have to correctly handle the case where a binary cannot be signed
> because it has references to unsigned assemblies. We run into this all the
> time with our UI controls.
>
> --
> John Merryweather Cooper
> Build & Install Engineer - ESA
> Jack Henry & Associates, Inc.®
> Shawnee Mission, KS 66227
> Office: 913-341-3434 x791011
> jocoo...@jackhenry.com
> www.jackhenry.com
>
>
>
> -Original Message-
> From: Dror, Tomer [mailto:tomer.d...@intergraph.com]
> Sent: Wednesday, December 18, 2013 1:44 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Signing all DLLs and EXEs in project
>
> If you can explain how do you want to sign the dll I can try to create wix
> extension for you
>
> something like
>
>
> yourNameSpace:SignKeyPathFile="yes"
>
> Guid="{87DFBD51-5DA7-46D2-9FB5-8A602A87EA71}"
>Id="ComponentAA1.txt">
> Source="Content\FeatureA\FeatureA1\ComponentAA1\ComponentAA1.txt"/>
>
>
>
>
>
>
>
> Tomer Dror
>
> SmartPlant Explorer Development Manager.
> Intergraph Corporation.
> Intergraph Israel.
>
> Nesher 36881 - 4, Hacharoshet St.
> P: +972 (4) 8779191-1222
>
> Skype:tomer.dee
> http://www.intergraph.com
>
>
>
> .
>
>
> From: Rob Mensching [r...@robmensching.com]
> Sent: Wednesday, December 18, 2013 9:26 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Signing all DLLs and EXEs in project
>
> Not today. Something considering for v4 (maybe).
>
> -Original Message-
> From: Brian Enderle [mailto:bria...@gmail.com]
> Sent: Wednesday, December 18, 2013 11:22 AM
> To: General discussion about the WiX toolset.
> Subject: [WiX-users] Signing all DLLs and EXEs in project
>
> Is there a way I can sign all the DLLs and EXEs in my project using WiX via
> signtool?
>
> I was hoping there might be something available in the @Component element
> that would allow me to selectively sign DLL/EXE files so that I could avoid
> signing DLLs that I did not create.
>
> Brian
>
> If you can't explain it simply, you don't understand it well enough. -
> Albert Einstein
> --
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> ___
> 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.
>
>
> --
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of ho
Re: [WiX-users] Signing all DLLs and EXEs in project
On 12/18/2013 1:21 PM, John Cooper wrote: > If you're signing more than a dozen or so files in one pass, you've got > bigger problems. :) Besides which, like many build-related tasks, signing > is an activity best done in the same project generating the binary. +1. Unless you're talking about signing custom action DLLs, then signing is best done before the packaging/installer task. -- Bruce -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: 0x80096005: timestamp signature and/or certificate could not be verified
On 1/28/2014 3:27 PM, Phill Hogland wrote: > There are other similar reports on the internet which are not related to Wix, > so the root problem is probably more along the lines that Christopher > suggested. When you recompiled did you consider using > MsiPackage/@SuppressSignatureVerification? This can happen if the machine can't contact the Microsoft servers to download the root certificate. At least on Vista, if the machine is never connected to the Internet our Burn packages won't install because the Verisign certificate isn't on the machine. I don't know if the same issue exists on Windows 7 and newer though. -- Bruce -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: util:ProductSearch logging 3 errors when no matching product found
I'm using WiX 3.9.120.0 - in Burn, is util:ProductSearch supposed to log errors when it doesn't find a matching product? I'm using: The log contains: [13E8:23D4][2014-01-30T12:01:15]e000: Error 0x80020005: Failed to copy variant value. [13E8:23D4][2014-01-30T12:01:15]e000: Error 0x80020005: Failed to change value type. [13E8:23D4][2014-01-30T12:01:15]i000: MsiProductSearch failed: ID 'wps1090C0D2C764DBC84EF5829FA1F83DB9', HRESULT 0x80020005 -- Bruce -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] UAC - random name
On Wed, 16 Feb 2011 10:21:33 -0500 Andreas Hiltner wrote: > Hi, > > When I install our generated MSI file, a dialog pops up, to ask the > user, if he wants to allow the "[insert random number here].msi" to > make any changes to the computer. > Now we would like to replace the "random number" with the name of the > MSI file or ProductCode. > How do I do that? > Maybe you could point me to the right area in the documentation. You can set it with the /d flag if you use signtool to sign the MSI. -- Bruce Cran -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Query about use of UAC shield on Install button
Hi, I have a question about the use of the UAC shield icon on the Install button when InstallPrivileges="elevated". According to http://msdn.microsoft.com/en-us/library/aa511445.aspx, "Tasks that require immediate elevation when UAC is fully enabled have entry points marked with the UAC shield. In this case, users should expect to see an Elevation UI immediately after clicking such commands...". But after clicking on "Install" the wizard moves onto the next page and it can take several seconds for the elevation prompt to appear. I'm wondering if WiX is going against the UI guidelines, or if they instead mean "immediate" in terms of workflow, not time - i.e. users aren't allowed to interact with the UI between clicking the button and getting the elevation prompt, though the UI can update? -- Bruce Cran -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Query about use of UAC shield on Install button
On Thu, 24 Mar 2011 13:07:30 + "Skildum, Mathew" wrote: > This is actually a function of MSI not WIX. WIX is just the > mechanism to build the MSI where the rules are enforced. > > MSI does follow these guidelines as far as I know. When you put the > UAC shield on a button that does not mean the elevation request will > happen right away. MSI does this request in the execute sequence > before the any files are copied or deferred actions are run as this > is the time when elevation is required. But as I understand it, it's WiX that controls whether or not the button has the shield icon: I'm wondering if it should use the shield icon on the button at all if the elevation request doesn't happen straight away. I'm tending towards yes, since it's a sign that the action that will occur will need to run as Administrator. -- Bruce Cran -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Query about use of UAC shield on Install button
On Thu, 24 Mar 2011 13:26:05 + "Skildum, Mathew" wrote: > Using the UAC shield is completely up to you not WIX. Since WIX is > just the development environment, the job of following guidelines > falls to the user. The WIX compiler can try to guide you down the > right path, but it should not force you to do any one thing. The > Button control XML has an option called "ElevationShield" which needs > to be enabled to show the icon. It's not entirely up to the user since WiX ships with standard UIs such as WiXUI_Minimal which provides buttons with the ElevationShield property set. -- Bruce Cran -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Query about use of UAC shield on Install button
On Thu, 24 Mar 2011 13:43:38 + "Skildum, Mathew" wrote: > Just because WIX ships a set of UI dialogs does not mean you need to > use them. > > I do not use any of the WIX dialogs and have create my own. This > allows me to enable and modify the UI whenever I wish. > > Due to this the choice is completely yours, if you use the standard > dialogs you get what is there or you can modify these to meet your > needs. Thanks. I intend to continue using WiXUI_Minimal since it completely meets my needs: I was wondering about future applications that I write in relation to the timing of the UAC prompt. Since Microsoft developers work on WiX I guess it's not seen as a major fault if an application doesn't elevate immediately after clicking a button with a shield icon. -- Bruce Cran -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Urgent Please help: Could not open key: HKEY_CURRENT_USER\Software\Classes\MyAppAssembly....
On Wed, 23 Mar 2011 13:51:55 -0700 (PDT) kim wrote: > I am confused as why the installer is trying to open this registry > entry?? > > I created 2 more installers using WIX 3.5 for Windows 7 and Windows > Server 2008 but never found this problem. This is only with Windows > XP SP3 box. > > Please suggest any solution to this problem. You should get a log by running "msiexec /l*vx msilog.txt /i . That'll tell you what the installer is doing at each step. -- Bruce Cran -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Generate SSL certificate during install time
On Tue, 19 Apr 2011 09:53:41 -0700 Thai-Hoa Nguyen wrote: > I'm looking for a way to create a SSL certificate during install > time. I don't think makecert.exe is allowed to distribute. Please > give me your suggestions. Could you use openssl to generate the certificates instead? -- Bruce Cran -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Why are we using a mailing list vs forum?
On Wed, 18 May 2011 12:57:22 -0600 john.bu...@telvent.com wrote: > There isn't a web interface; It's just an archive. So no posting or > un-read markers. I think both ways would be compatible (web forum > interface and mailing list interface). That'd be kind of neat. How about http://comments.gmane.org/gmane.comp.windows.devel.wix.user/55266 ? -- Bruce Cran -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] size of installation in Add\Remove programs applet
On Tue, 24 May 2011 16:49:18 +0400 Sergey wrote: > I found in google that i can use ARPSIZE property to give ARP a hint, > what is the size of installation. > But i can not write fixed value for this property in WIX project, > because size depends on features, user selects to install. > How can i set ARPSIZE according to real total size of files, user > selected to install? > Are there some other solutions of this problem? I don't know if it helps, but http://technet.microsoft.com/en-us/magazine/gg558108.aspx explains how the size is estimated. -- Bruce Cran -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom dialogs in wix 3.5?
On Wed, 15 Jun 2011 07:54:43 -0700 Nuno Romao wrote: > I'm just now migrating a wix project from wix 3.0 to wix 3.5. My 3.0 > project had a customization of InstallDirDlg.wxs to allow the user to > decline creation of a desktop icon. To add this customization > required modification of the InstallDirDlg.wxs file that was part of > the wix 3.0 source. It seems that source for 3.5 is not available (or > I can't find it). How can I move to 3.5 and still have a checkbox to > disable creation of a desktop icon? The code for WiX 3.5 can be found at http://wix.codeplex.com/SourceControl/list/changesets?branch=wix35 . By the way I think Microsoft recommends a desktop icon not be created by default. -- Bruce Cran -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: Community package definitions
On 28/06/2011 23:08, Dan Puza wrote: > For example, I just made a separate post asking about problems I'm having > bootstrapping Windows Installer 4.5 and SQL Server 2008. I wouldn't wish the > trial and error pain and time on anybody duplicating the same effort. That > doesn't seem like it should be necessary. Someone figures it out once and > that's it, everyone benefits. There are some good answers on stackoverflow.com. For example http://stackoverflow.com/questions/471424/wix-tricks-and-tips . I think you can also make wiki entries there. -- Bruce Cran -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstalling driver package with DPInst
On 04/07/2011 08:56, Yuk Hei Pang wrote: > Hi, I am currently having a msi created with wix 3.5 to install a driver > package along with an application. > The following custom action is used for uninstalling the driver package. > > I know this doesn't answer your question, but I think Microsoft recommends not uninstalling the driver when a user runs the uninstallation entry. -- Bruce Cran -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: bootstrap a single MSI, not showing BA UI at all
I'm just starting to use Burn and was wondering if it's possible to use it to simply 'wrap' an MSI as a .exe and have it not show any of its own UI? That is, launching the executable should only show the internal MSI interface. Is that possible using the standard BA, or would I have to write my own? -- Bruce Cran -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] BA: Shutdown() or Quit()?
The documentation for Burn says that a BA should call Shutdown() when it's finished. However, there doesn't seem to be such a method, while Quit() does exist. Has this been renamed at some point and the documentation is lagging behind? -- Bruce Cran -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn UI
On 25/10/2011 18:47, Neil Sleightholm wrote: > Is it possible to use the standard WiX authored MSI dialogs as the UI for > Burn? I asked about this yesterday: the BA that comes with Burn has a toggle to show the MSI UI, but it will still show its own interface too. You'd need to write your own BA to do this. See the thread "Burn: bootstrap a single MSI, not showing BA UI at all" for Rob's answer :) -- Bruce Cran -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn UI
On 25/10/2011 22:12, Neil Sleightholm wrote: > I guess I was hoping for something for free, the current BA UI doesn't look > very nice if the WIX install is anything to go by I as I don't really write > UI's I was look for a "free lunch"! Actually, the UI in the WiX installer is especially ugly - the UI that developers get via Burn is much nicer (without the RSS feed, a different layout etc.), if incomplete in places. For example there's no explanation that a reboot is required at the end, just "Reboot" and "Close" buttons. -- Bruce Cran -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Weekly update is missing / message from sourceforge
On 26/10/2011 09:17, Albert van Peppen wrote: > I've modified the title of this thread, since it has nothing more to do with > installation problem :) > > My archive, for those who didn't knew yet, is at > http://madbutcher.dyndns.org/snippets/WiX/ > I try to keep it up to date as much as possible :) I've also started creating a mirror at http://bluestop.org/wix - currently just a few files from codeplex exist at http://bluestop.org/wix/releases/ . I think I have plenty of bandwidth to support it. -- Bruce Cran -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Weekly update is missing / message from sourceforge
On 26/10/2011 16:05, Albert van Peppen wrote: > I would like to automate this but on codeplex there are several obstacles to > take: > - You need to download via the website and accept the agreement (not easy to > automate, that's the idea of it I suppose) > - There is no history.txt so I need to get that one out of the source-zip file > > On sourceforce I haven't yet tried, but as far as I understand, the files > will no longer be put on there? > > If you give me a (deep)link where I automatically can download the latest > set, I'm happy to automate the mirroring :) I guess the weekly builds won't appear on codeplex due to issues around automating the uploads? I don't know what sort of server wixtoolset.org is on, but I was expecting they'd appear there, as the authoritative source. If not, then it may be possible for me to configure my server for a weekly rsync or something since I already do that for hosting other open source software. -- Bruce Cran -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Configuring the version information in the bootstrapper?
I was wondering, are there any plans to allow the various version properties in the WiX bootstrapper to be customised, even if the developer doesn't want an entry to be created an ARP? Or, is it a feature that all bootstrapper executables are 'advertised' as having been created by WiX? For example, the following can't be changed at the moment: File description: WiX Toolset Bootstrapper Product name: Windows Installer XML It might be nice if a new property could be added to control whether or not the ARP entry is created for the bootstrapper, while allowing Manufacturer and Name to still be used to customize the executable properties. -- Bruce Cran -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn UI
On 27/10/2011 18:25, Neil Sleightholm wrote: > Out of interest do people think there is a demand for wizard style install? > Personally I still think they are correct approach and I haven't seen a good > alternative yet. I tend to agree. I know Apple don't always do things right, but they still use multi-page wizard applications on OS X for things like installing XCode. -- Bruce Cran -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] DIFx: MsiProcessDrivers, WdfPostDeviceRemove and scheduling
I'm writing an installer for a WDF driver, and am finding that MsiProcessDrivers is being run after files have been removed. The problem is that according to the documentation, I need to run WdfPostDeviceRemove() after the service has been deleted - which requires WdfCoInstaller01009.dll to be loaded. Since that's already been deleted, my custom action is failing. Should I be scheduling MsiProcessDrivers earlier in the InstallExecute sequence, or do people just avoid DIFx and use DPinst etc. for drivers? -- Bruce Cran -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] DIFx: MsiProcessDrivers, WdfPostDeviceRemove and scheduling
On 03/11/2011 11:54, Bruce Cran wrote: > I'm writing an installer for a WDF driver, and am finding that > MsiProcessDrivers is being run after files have been removed. The > problem is that according to the documentation, I need to run > WdfPostDeviceRemove() after the service has been deleted - which > requires WdfCoInstaller01009.dll to be loaded. Since that's already been > deleted, my custom action is failing. Should I be scheduling > MsiProcessDrivers earlier in the InstallExecute sequence, or do people > just avoid DIFx and use DPinst etc. for drivers? Sorry, I've just realised this would probably be better on StackOverflow etc. since it's not really a WiX question. -- Bruce Cran -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX 3.6 and System.ArgumentException ("illegal characters in path") during build
I'm using WiX 3.6.2221.0 and am having problems trying to build using msbuild.exe. Most of the time the build is failing with System.ArgumentException: light.exe : error LGHT0001: Illegal characters in path. [C:\cygwin\home\mymsi.wixproj] Exception Type: System.ArgumentException Stack Trace: at System.IO.Path.CheckInvalidPathChars(String path) at System.IO.Path.IsPathRooted(String path) at Microsoft.Tools.WindowsInstallerXml.BinderFileManager.ResolveFile(String source, String type, SourceLineNumberCollection sourceLineNumbers, BindStage bindStage) at Microsoft.Tools.WindowsInstallerXml.Binder.ResolveFields(TableCollection tables, Hashtable cabinets, ArrayList delayedFields) at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String databaseFile) at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String file) at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) Has anyone else come across this and know what the problem might be? -- Bruce Cran -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.6 and System.ArgumentException ("illegal characters in path") during build
On 08/11/2011 19:03, Bruce Cran wrote: > light.exe : error LGHT0001: Illegal characters in path. > [C:\cygwin\home\mymsi.wixproj] It turned out that I had a stray " in one of my variables which was being used in a path. -- Bruce Cran -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Failed to install WiX v3.6
On 16/11/2011 12:06, Harper wrote: > What's wrong? How can I get information, why it failed? And how can this be > fixed? One thing that's different from a successful installation is that it > failed on a computer that's a member of a domain. But I am not aware of > policies that disallow software installation. > > How do I get WiX 3.6 installed? One way it can fail is if Windows Installer has any reboots pending - for example if you've installed something previously that wanted to reboot and you clicked "No". Otherwise, you could check in the logs it produces by default (i.e. logging is enabled by default) in %TEMP% . -- Bruce Cran -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Error LGHT1055 when linking both VC100 CRT and MFC merge modules
Hi, I'm trying to add both the Visual C++ 2010 CRT and MFC merge modules to my project, but when I link I get: 2>Product.wxs(23): error LGHT1055: The AdminUISequence table contains an action 'CA_WindowsFolder_amd64_VC.585D293E_BFCC_3045_857D_FFD4B0225AB6' which cannot be merged from the merge module 'C:\Program Files (x86)\Common Files\Merge Modules\Microsoft_VC100_MFC_x64.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module. [project.wixproj] I'm using the following Merge statements: Does anyone know how to fix this? -- Bruce Cran -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] PhysicalMemory issue
On 23/11/2011 14:56, Nicolas Penin wrote: > I am adding Launch conditions to my installer made with wix 3.6. However, I > am fighting with the PhysicalMemory property which actually reports the ram > usable and not the installed ram on a 32-bit Windows 7. I'm not sure what you mean by "ram usable". If Windows can only see/use 3 GB since you're running 32-bit Windows and you've installed 8 GB then you really don't want PhysicalMemory to report 8 because nothing can use anything above 3. -- Bruce Cran -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error LGHT1055 when linking both VC100 CRT and MFC merge modules
On 22/11/2011 18:19, Bruce Cran wrote: > I'm trying to add both the Visual C++ 2010 CRT and MFC merge modules to > my project, but when I link I get: > >2>Product.wxs(23): error LGHT1055: The AdminUISequence table > contains an action > 'CA_WindowsFolder_amd64_VC.585D293E_BFCC_3045_857D_FFD4B0225AB6' which > cannot be merged from the merge module 'C:\Program Files (x86)\Common > Files\Merge Modules\Microsoft_VC100_MFC_x64.msm'. I forgot I'd enabled 'warnings as errors', so now they're just warnings I can ignore. -- Bruce Cran -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to disable CA if feature not installed
On 24/11/2011 02:45, Michael Janulaitis wrote: > What does '=3' mean? See http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012%28v=vs.85%29.aspx -- Bruce Cran -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] weekly updates
On 30/11/2011 09:07, Sean Farrow wrote: > Hi: > Havv3.6.2221.0? > I don't see any and wondered whether updats had moved. > Regards > Sean.e there been any weekly updates later than That's an impressively mangled email! I believe there's a plan being worked out since the bandwidth quota was being exceeded on Sourceforge and so the weekly builds had to be removed. -- Bruce Cran -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] weekly updates
On 30/11/2011 11:00, Albert van Peppen wrote: > If someone of the wix team can provide me with the weekly set I am more than > happy to put it on my WiX mirror. > But as said, there are currently no weekly releases, to my knowledge, so I > can't update my mirror. :( You could always create your own - just do a weekly "hg pull -u", build the code and upload the files. -- Bruce Cran -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting msi's file version
On Mon, 14 Dec 2009 12:42:51 -0500 Tony wrote: > Is it possible to place a file version property (not to be confused > with Windows Installer properties) on the resulting msi from a WiX > build? Such that when you hover over the msi in explorer the version > is displayed? > > Not a big deal, just wondering... See the 1st answer at http://stackoverflow.com/questions/151250/how-do-i-embed-a-file-version-in-an-msi-file-with-visual-studio -- Bruce Cran -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Expanding an env var at install time when writing to the registry
I've written an installer with WiX 3.5 which installs a Winsock provider, netsh helper and a kernel driver. After doing some restructuring I started getting a warning about installing a non-permanant component into system32, so I'm now trying to change the installation location to be under %ProgramFiles%\Product . However, I need to create a registry entry which points to the new location so that netsh can find it, and it seems that netsh doesn't understand REG_EXPAND_SZ types. Is there a way to write a string to a REG_SZ type during installation which already has the environment variables expanded, or would I need to write a custom action? I've also been wondering what the best location for the winsock provider and netsh helper is, since they extend system functionality - and to install both 32-bit and 64-bit provider DLLs will require creating both C:\Program Files\Product and C:\Program Files (x86)\Product. Applications seem to differ between installing files under system32, CommonProgramFiles and under ProgramFiles and the only advice I've read is that files shouldn't be installed under system32 any more. -- Bruce Cran -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.5 Help file
On Thu, 17 Dec 2009 20:57:16 - "Neil Sleightholm" wrote: > I downloaded WiX 3.5.1204.0 binaries and the help file doesn't seem to > work, it loads ok but the right hand pane displays "Navigation to the > webpage was cancelled" - is anyone else seeing this (the DTF help > files also fail in the same way). CHM files only work if they're trusted: that normally means they need copied to a local disk first, and if downloaded from the Internet they need unblocked - in the General tab of the file's Properties, click 'Unblock'. -- Bruce Cran -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Clarification on the MSI security
On Mon, 21 Dec 2009 22:21:47 -0800 (PST) Andy2k8 wrote: > > If anybody can use the orca tool to edit a shipped MSI package, are > we not compromising on the security of the installer database? Or is > there any way i can make my MSI read only? You can sign MSI files using an Authenticode signature: if someone modifies the database after it has been signed then the signature will be marked as invalid and any user attempting to run/open it will be warned that it has been changed. -- Bruce Cran -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 32/64-bit setups
On Mon, 28 Dec 2009 08:30:58 - "Sean Farrow" wrote: > Hi: > > Is it possible to build one msi package that runs natively on both > 32and 64 bit setups using Wix? If yes how wouldthis be done? If no is > it possible to set pre-processor defines with the votive ui for > specific configurations? No, it's not possible. See http://blogs.msdn.com/astebner/archive/2007/08/09/4317654.aspx for a discussion of a solution. It's also been discussed on this list too. The installer I created recently creates both x86 and x64 MSIs - you can see the sources at http://www.bluestop.org/viewvc/repos/sctpDrv/wix/ -- Bruce Cran -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major Upgrades and Versions
On Thu, 14 Jan 2010 15:16:05 -0500 "Castro, Edwin G. (Hillsboro)" wrote: > We have an automated build that runs continually. We'd like each MSI > produced to behave as a major upgrade so that we can apply any newer > MSI on a target environment easily. Our build process fixes the first > two parts of our version numbers to predetermined values and allows > the remaining two values to vary on a per-build basis. I understand I > need to change produ...@id and produ...@version with every build > while keeping produ...@upgradecode constant to implement major > upgrades. If produ...@version changes from 1.2.3 to 1.2.4 will the > MSI produced behave as a major upgrade? You can set Product/@Id to "*" to automatically produce a new Id. -- Bruce Cran -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Avoiding hard-coding the path to the WiX SDK when using the WDK
I'm using the WDK to build a C++ custom action DLL that gets included in my MSI that I create using WiX 3.5. The problem I've come across is that the WiX headers are located in C:\Program Files (x86)\Windows Installer XML v3.5\SDK\inc, and the WDK doesn't appear to recognise long filenames. I've tried adding $(WIX)SDK\inc both with and without quotes to the 'sources' file, but the only thing that works is using C:\PROGRA~2\WINDOWS~1.5\SDK\doc. I'd rather not use that because it'll be wrong on 32-bit Windows. Does anyone know a way around this to avoid hard-coding paths that other developers are going to have to change for their machines? -- Bruce Cran -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Problems with DIFxAPP and major upgrade
Hi, I'm having problems doing a major upgrade. I'm using WiX 3.5 to install a driver using DIFxAPP and start it using ServiceControl: Everything goes well during an installation, but I've seen issues both during uninstall and a major upgrade: if I try and uninstall SctpDrv before the DIFx driver package, it claims to have failed but it does complete the uninstallation; during a major upgrade it removes the previous version but fails to complete the upgrade, with DIFxAPP erroring out with: DIFXAPP: ERROR: Unable to revert to a previous driver store for service 'Sctp'. DIFXAPP: ERROR: Will attempt to uninstall the driver. DIFXAPP: ERROR: Error unable to open service 'Sctp' to delete it because of error 0x424 DIFXAPP: ERROR: Error occurred while deleting service to uninstall the driver store. DIFXAPP: ERROR: We were unable to install any other driver store entry to support the service Sctp and we also failed to delete the service. DIFXAPP: ERROR: Failed to uninstall the driver. Attempting to undo system changes ... (Error code 0x643: Fatal error during installation.) It leaves the driver package entry present, but with SctpDrv uninstalled. the only strange thing I've noticed is that the driver and netshell helper is listed twice in the list of components: MSI (s) (44:C0) [17:09:02:640]: Feature: Complete; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: ws2sctp.h; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: echo_client.c; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: echo_server.c; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: echo_server2.c; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: spinstall.exe; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: echo_client.exe; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: echo_server.exe; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: sctpmon.dll; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: sctp.inf; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: sctp.cat; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: sctp.sys; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: sctpsp.lib; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: libsctpsp.a; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: README.txt; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: CHANGES.txt; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: SctpDrv.chm; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: sctpsp32.dll; Installed: Local; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: __sctpmon.dll65; Installed: Null; Request: Absent; Action: Absent MSI (s) (44:C0) [17:09:02:640]: Component: __sctp.sys65; Installed: Null; Request: Absent; Action: Absent Am I misunderstanding how to use DIFxAPP, or is there another problem with my WiX sources? The Upgrade section I'm using is: with RemoveExistingProducts scheduled after InstallInitialize. The msi log is available at http://www.bluestop.org/SctpDrv/tmp/msi_log_20100115.txt - the source file containing the components is at http://www.bluestop.org/viewvc/repos/sctpDrv/wix/module-common.wxs?revision=44&view=markup . -- Bruce Cran -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Avoiding hard-coding the path to the WiX SDK when using the WDK
On Sat, 16 Jan 2010 01:51:45 -0800 "Blair" wrote: > Install WiX to a different folder? I guess that's probably the only solution. I was hoping to avoid that since the directory under Program Files is the default location, and anyone who wants to build my project will need to have a custom installation too. -- Bruce Cran > > -Original Message- > From: Bruce Cran [mailto:br...@cran.org.uk] > Sent: Friday, January 15, 2010 5:06 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Avoiding hard-coding the path to the WiX SDK > when using the WDK > > I'm using the WDK to build a C++ custom action DLL that gets included > in my MSI that I create using WiX 3.5. The problem I've come across > is that the WiX headers are located in C:\Program Files (x86)\Windows > Installer XML v3.5\SDK\inc, and the WDK doesn't appear to recognise > long filenames. > > I've tried adding $(WIX)SDK\inc both with and without > quotes to the 'sources' file, but the only thing that works is using > C:\PROGRA~2\WINDOWS~1.5\SDK\doc. I'd rather not use that because > it'll be wrong on 32-bit Windows. > > Does anyone know a way around this to avoid hard-coding paths that > other developers are going to have to change for their machines? > -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Avoiding hard-coding the path to the WiX SDK when using the WDK
On Sat, 16 Jan 2010 11:18:23 +0100 "Sebastian Brand \(Instyler Software\)" wrote: > Why not just copy the header files to your own folder? Thanks, I think that's probably the best solution - I've modified the batch file I use to check that prerequisites are installed and which launches the build so that it copies all the headers, libraries and tlb files from 'Program Files' to 'inc' and 'lib' directories under my project first. -- Bruce Cran -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Testing installers
On Sat, 30 Jan 2010 14:11:43 - "Ryan O'Neill" wrote: > Has anyone found a good solution for testing MSI based installers? I'm > thinking of putting together a virtualised test system to cover the > major OS/platform/Service pack combinations and wondered if there was > a system that could do this already? Otherwise I'll have to do all > the MSI button clicking via an automated script and that might take > some time. I've not come across anything specifically for testing installers, but I guess a combination of VMWare and Sikuli would work well. VMWare allows you to automate the installation of Windows, take snapshots and replay failures for debugging, and from watching the demos at http://groups.csail.mit.edu/uid/sikuli/ it seems Sikuli is flexible enough to automate the button clicking involved in installing an application through MSI. -- Bruce Cran -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows Installer XML toolset version 3.0.4805
On Wednesday 17 February 2010 08:01:35 iPetr wrote: > Hello! > I need the Windows Installer XML toolset version 3.0.4805. Can any body > provide me this version of WiX? > You should be able to get the specific version from the repository and build it yourself. -- Bruce Cran -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Shared DLL install locations
I've created an installer for a driver. It installs the driver itself, 32-bit and 64-bit DLLs and import libraries. 3rd-party applications will link to the DLL in order to use the driver. I know that I shouldn't install files to system32, but if not there then where? If I install to Program Files then the applications won't find the DLLs at runtime, forcing the users to either copy them to system32, or to their own application directory. I've been unable to find any Microsoft documentation recommending locations. -- Bruce Cran -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Unresolved symbols from _filevers...@12 in WiX 3.5.1710.0
I upgraded WiX from a version from a couple of months ago to 3.5.1710.0 and started getting the following linker errors: 4>c:\users\bruce\desktop\sctpdrv\wix\dutil.lib(fileutil.obj) : error LNK2019: unresolved external symbol _verqueryval...@16 referenced in function _filevers...@12 4>c:\users\bruce\desktop\sctpdrv\wix\dutil.lib(fileutil.obj) : error LNK2019: unresolved external symbol _getfileversionin...@16 referenced in function _filevers...@12 4>c:\users\bruce\desktop\sctpdrv\wix\dutil.lib(fileutil.obj) : error LNK2019: unresolved external symbol _getfileversioninfosi...@8 referenced in function _filevers...@12 4>c:\users\bruce\desktop\sctpdrv\wix\objfre_wxp_x86\i386\setup.dll : error LNK1120: 3 unresolved externals Do I need to link in another library, or has something else changed recently? -- Bruce Cran -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Unresolved symbols from _filevers...@12 in WiX 3.5.1710.0
On 13/05/2010 06:11, Bruce Cran wrote: > I upgraded WiX from a version from a couple of months ago to 3.5.1710.0 > and started getting the following linker errors: > Sorry, I saw the answer just seconds after posting: I needed to add version.lib. -- Bruce Cran -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Stopping/deleting a DIFxApp driver when uninstalling
Hi, I'm having problems getting my driver/service to stop and delete itself when uninstalling my package - I'm currently testing on Vista x86, but I've seen the problem on XP and Windows 7 too. In my WiX file I have: The sctp service (a kernel driver) works without problems during installation but it never gets stopped or removed during uninstallation. Also, the entry remains in the "Programs and Features" window until I close and re-open it, while I'd expect the entry to be removed as soon as the uninstallation had finished. I'm using WiX 3.5.1728.0. Is this a limitation of DIFxApp, or am I missing something in my WiX sources? -- Bruce Cran -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Stopping/deleting a DIFxApp driver when uninstalling
On Thu, 03 Jun 2010 08:17:32 -0400 Bob Arnson wrote: > On 6/2/2010 10:47 AM, Bruce Cran wrote: > > >> Stop="both" Remove="uninstall"/> > > That might work but note that MSI explicitly says it doesn't support > drivers as services. > > > The sctp service (a kernel driver) works without problems during > > installation but it never gets stopped or removed during > > uninstallation. > > As I recall, that's usually handled via flags in an .inf file; > DifxApp doesn't do it directly. > Thanks, that was the problem: after adding the 0x800 flag (start the service after installation) into the AddService line in the INF file and removing the ServiceControl line everything works as expected, including the service being stopped and the driver file deleted! -- Bruce -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] createAndRemoveOnUninstall for registry VALUE?
On Wed, 12 May 2010 00:20:05 +0200 Kristoffer Danielsson wrote: > It seems "createAndRemoveOnUninstall" works on the key. How would you > use that logic only on the value under the specified key? That is, > the key should not be removed - only the its sub value > "InstalledComponent1". The registry values are automatically created during installation and removed during uninstallation as standard. -- Bruce Cran -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ProgramFilesFolder and ProgramFiles64Folder, GUIDs and merge modules
Hi, I've just moved the majority of my installer logic to a merge module to enable users to integrate the product into their own installers. However when building a 64-bit MSI, I now get the following warnings: light.exe : warning LGHT1076 : ICE82: This action ProgramFilesFolder.CBD780C2_8B E5_4537_B7EC_5D2268D62C65 has duplicate sequence number 1 in the table InstallExecuteSequence It appears to be occurring because both ProgramFilesFolder and ProgramFiles64Folder have have the same sequence number of 1. They also have the same GUID - should they? I guess that since there are no dependencies between the directories it shouldn't matter which gets installed first, but I'd like to get rid of the warning if possible. -- Bruce Cran -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Build 3.5.1902.0 MSI broken on Windows 7 amd64?
Hi, I had an older build of WiX 3.5 installed so I uninstalled it and tried installing build 3.5.1902.0 from http://wix.sourceforge.net/releases/3.5.1902.0 . However, I click "Install" and get to the WelcomeDlg, but can't proceed because the "Next" button doesn't do anything. I've uploaded the log to http://www.cran.org.uk/~brucec/wix35_3.5.1902.0_log.txt.txt -- Bruce Cran -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error when tryin to install the latest drop of the wix toolset
On Sun, 4 Jul 2010 09:47:09 +0100 "Sean Farrow" wrote: > When trying to install the latest drop of the Wix toolset the > installation doesn't proceed past the install feature selections > dialog. It takes me back to what looks like the welcome dialog. It's a known issue: > Yep, the new patch dialogs are busted on WixUI_Advanced. For a > temporary workaround, install from the command line with /qb. -- Bruce Cran -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: associating checkbox with feature installation of specific MSI?
Is there currently any simple way to associate a checkbox with feature installation for a specific MSI? From what I've read the only way would be to do conditional installation with ADDLOCAL MsiProperty's set to the feature name, e.g. -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: FailureRestartText mentions 'rollback'
When a reboot is pending, Burn fails with the message: You must restart your computer to complete the rollback of the software. I'm wondering why it mentions 'rollback' because in this case the reboot is pending following a successful installation of a driver. -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixStdBA: options browse dialog doesn't work in Server Core
Should WixStdBA work on Server Core? It mostly seems to, but Options -> Browse isn't functional since Core doesn't have the common dialogs - apparently it can be made to work by adding some flags (http://social.technet.microsoft.com/Forums/en-GB/winservercore/thread/f9f1f6f1-960a-4ddf-94d4-86b7ce3796bb). -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: associating checkbox with feature installation of specific MSI?
On 13/11/2012 15:49, Rob Mensching wrote: > What about using a Feature/Condition instead? Thanks, that works. -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: won't /layout with reboot pending
I understand the reason for blocking installation if a reboot from a previous installation hasn't occurred, but shouldn't users be able to layout installation files without rebooting? I just found that the VS2012 Update 1 installer required a reboot before it would download the installation files. -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wcautil.lib in 3.7 RC: LNK4099 warnings (vc110.pdb not found; linking as if no debug info)
Something seems to have changed with the way wcautil.lib and dutil.lib (at least) are built betwen 3.6 and 3.7 RC - I've started getting warnings like: dutil.lib(strutil.obj) : warning LNK4099: PDB 'vc110.pdb' was not found with 'dutil.lib(strutil.obj)' or at 'C:\Release\vc110.pdb'; linking object as if no debug info wcautil.lib in 3.7 is 528KB vs. 1.5MB in 3.6. What's changed, and should I update my project settings to fix the warning? -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Bootstrapper Bundle creating uninstall shortcut in program files
On 27/11/2012 17:18, rpriest12 wrote: > I am in the same boat - I need the product code. there seem to be several > questions about this for various reasons. Surely the answer can be to troll > the uninstall registry key looking for "Bundle*"? What if you have multiple > applications that installed using Burn? I have two on my box now. Am I > supposed to compare strings? surely exposing the Product Code and allowing > it to be set to something static would be better... You could use the upgrade code instead - there's a BundleUpgradeCode entry in the Uninstall key, though I'm not sure it's documented and so might disappear. -- Bruce Cran -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Extract packages from bootstrapper?
On 30/11/2012 21:24, StevenOgilvie wrote: > Can I extract the packages/msi's from the exe for someone using GPO? Currently the only way is using dark.exe - there's a feature request open on the sourceforge tracker to add a /extract switch to WixStdBA so anyone can get a copy of the embedded packages. -- Bruce Cran -- Keep yourself connected to Go Parallel: TUNE You got it built. Now make it sing. Tune shows you how. http://goparallel.sourceforge.net ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Extract packages from bootstrapper?
On 30/11/2012 21:39, Steven Ogilvie wrote: > Thanks very much Bruce... > > Do you know if this will be done for 3.7? Since we've had 3.7 RC I suspect not. I suspect it's quite low down the priority list and so would need someone to contribute a patch. -- Bruce Cran -- Keep yourself connected to Go Parallel: TUNE You got it built. Now make it sing. Tune shows you how. http://goparallel.sourceforge.net ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixStdBA retry 'cancel' button not working?
Has anyone else found that the "cancel" button on the error retry dialog in WixStdBA doesn't work (in 3.7 RC)? I find clicking it displays the same error with an OK button before just retrying anyway. The error when this occurs is "Could not access network location". -- Bruce Cran -- Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] v3.7.1126.0 on Monday, November 26, 2012
On 03/12/2012 20:16, Neil Sleightholm wrote: > I just tried again with 7-zip and do indeed get the "Unsupported Compression > Method for" error but the files do extract ok - personally I think there is a > bug in the compress code. I get "unsupported compression method" for directories, but none of the files. -- Bruce Cran -- Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixStdBA retry 'cancel' button not working?
On 04/12/2012 15:06, Rob Mensching wrote:
> Can you share a chunk of the log file for that. I expect the issue is the
> automatic retry code on errors is incorrectly catching this scenario.
[07E0:0640][2012-12-03T14:00:33]i301: Applying execute package:
package.msi, action: Install, path: C:\ProgramData\Package
Cache\{guid}v1.0.0.0\package.msi, arguments: ' ALLUSERS="1"
ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" APPLICATIONFOLDER="C:\Program
Files\Install"'
[07E0:0640][2012-12-03T14:01:12]e000: Error 0x80070643: Failed to
install MSI package.
[07E0:0640][2012-12-03T14:01:12]e000: Error 0x80070643: Failed to
execute MSI package.
[0654:0178][2012-12-03T14:01:12]e000: Error 0x80070643: Failed to
configure per-machine MSI package.
[0654:0178][2012-12-03T14:01:12]w348: Application requested retry of
package: package.msi, encountered error: 0x80070643. Retrying...
[07E0:0640][2012-12-03T14:01:15]i301: Applying execute package:
package.msi, action: Install, path: C:\ProgramData\Package
Cache\{guid}v1.0.0.0\package.msi, arguments: ' ALLUSERS="1"
ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" APPLICATIONFOLDER="C:\Program
Files\Install"'
[07E0:0640][2012-12-03T14:02:08]e000: Error 0x80070643: Failed to
install MSI package.
[07E0:0640][2012-12-03T14:02:08]e000: Error 0x80070643: Failed to
execute MSI package.
[0654:0178][2012-12-03T14:02:08]e000: Error 0x80070643: Failed to
configure per-machine MSI package.
[0654:0178][2012-12-03T14:02:08]w348: Application requested retry of
package: package.msi, encountered error: 0x80070643. Retrying...
--
Bruce Cran
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Feature or Chained MSI?
On 05/12/2012 15:15, Rob Mensching wrote: > I would definitely consider using a Bundle for your scenario. I believe the > world is moving (has moved?) to a place where .msi files are building > blocks stacked together and wrapped with a bootstrapper (Burn Bundles in > WiX toolset). You do need to think about the problem a little differently > when using Bundles because you'll get many more degrees of freedom which > may come with a bit extra work (particularly in the UI department) since > Bundles are still pretty young. Something I've been wondering is how automated deployment is supposed to work. I've not used GPO, but I think it needs a .msi file in order to install an application? -- Bruce Cran -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WDK 8.0, Driver Verifier and XP/2003 compatiblity
I know this isn't recommended, but is there some incompatibility between WDK 8.0 and XP/2003 that prevents drivers running correctly with Driver Verifier? We're finding that when Driver Verifier is enabled our driver gets so far initializing and then any memory allocation calls end up calling ExFreePoolWithTag and the driver hangs in RtlpUnwindPrologue (it runs fine without DV enabled). The system's still active, but the driver just never gets any further. -- Bruce Cran -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
