Re: [WiX-users] Question about Properties and Custom Actions
Thanks for the replies. You can use MsiSetTargetPath() in your custom action to update an existing directory Id. That would more closely model your intent and requires less code. Good point, that's another option. I have been looking at what was done in the WixQueryOsDirs custom action - there they used secure public properties rather than MsiSetTargetPath. I don't know why - maybe because that extension defines about 20 different paths, most of which wouldn't be used in a particular installer? Pete -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Question about Properties and Custom Actions
I'd just like a bit of advice/clarification on property types and CAs. If I write a CA to fetch a folder location from the OS (to be used like 'ProgramFilesFolder') then I need to set a property (correct?) If I use a private property I have to give it a 'default' value which is overwritten by the CA - but then I always get ICE48. So do I have to use a secure public property? This seems OK but I'm not sure (despite having read the docs!) I understand the nuances of secure public properties vs. private properties when it comes to elevated installs - could someone please explain it in a sentence or two? Thanks Pete -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing Device Metadata Package
It looks like it might be a fairly simple extension to the OSInfo part of WixUtilExtension/wixca. I will see if I can put something together for this. Pete From: peterhul...@hotmail.com To: wix-users@lists.sourceforge.net Date: Tue, 25 Sep 2012 09:27:21 +0100 Subject: [WiX-users] Installing Device Metadata Package I would like to use WiX to install a device metadata package. This needs to go into a sub-folder of a folder identified by a KNOWNFOLDERID (specifically FOLDERID_DeviceMetadataStore) The same question was asked back in 2009 ( http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-Device-Metadata-on-Windows-7-td3554946.html ) and the answer from Bob Arnson was about creating a custom action to set a property. I would like to know, is this still the best way to do it? I haven't made a custom action before but I am prepared to learn how to, unless with the latest WiX there's another method. If possible I would try and make something more general and contribute it back to the project. Any comments welcome, Pete -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Installing Device Metadata Package
I would like to use WiX to install a device metadata package. This needs to go into a sub-folder of a folder identified by a KNOWNFOLDERID (specifically FOLDERID_DeviceMetadataStore) The same question was asked back in 2009 ( http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-Device-Metadata-on-Windows-7-td3554946.html ) and the answer from Bob Arnson was about creating a custom action to set a property. I would like to know, is this still the best way to do it? I haven't made a custom action before but I am prepared to learn how to, unless with the latest WiX there's another method. If possible I would try and make something more general and contribute it back to the project. Any comments welcome, Pete -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major Upgrade changes requirement
Date: Thu, 30 Aug 2012 18:03:02 -0400 From: mukeshj...@kpmg.com To: wix-users@lists.sourceforge.net Subject: [WiX-users] Major Upgrade changes requirement What changes we need to do for Major Upgrade Example - Product Code, Package Code, version etc... ?? There's a section in the WiX help file called 'How To: Implement a Major Upgrade In Your Installer' which I found very useful. Also the MSDN section is good for background: http://msdn.microsoft.com/library/aa369786.aspx Pete -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX joins the Outercurve Foundation
Thanks, that does help. If I could just ask the question slightly differently: If I modified the WiX source, as I understand it, I would need to licence my changed WiX source under MS-RL and make it freely available. If I downloaded a binary of the WiX toolset and then used that toolset (unchanged) to create an installer, what would I need to make available? Pete -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX joins the Outercurve Foundation
From: edwin.cas...@fiserv.com Date: Wed, 15 Aug 2012 12:12:44 -0400 I think it is important to ask these questions if only to determine the intentions of the licensors and encourage that the license be more explicit about its intentions. These things should not be determined in court after the fact. I agree with you, Edwin. It would be really helpful if Rob, Bob or someone from Outercurve could comment on the license and how it applies to WiX. I guess they know the answer straight off; it's useless for us to speculate on the exact interpretation of the license terms and how it applies to the different scenarios (e.g. using Burn, using WiX extensions, embedding CABs, ...) Pete -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX joins the Outercurve Foundation
Date: Tue, 14 Aug 2012 21:06:07 +0100 From: br...@cran.org.uk I'm a bit surprised that the license change wasn't highlighted - it seems WiX is now licensed under the Ms-Rl. I would appreciate some clarification on this license too. (A) Reciprocal Grants- For any file you distribute that contains code from the software (in source code or binary format), you must provide recipients the source code to that file along with a copy of this license, which license will govern that file. You may license other files that are entirely your own work and do not contain code from the software under any terms you choose. A Burn bundle contains WiX code in binary format so what source code do I need to provide? The .wxs file? Or the source code to my program? Peter -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI detected as virus.... RunOnce registry keys
This has been seen before and reported as a bug: http://sourceforge.net/tracker/?func=detailaid=3431068group_id=105970atid=642714 I believe it only affects Windows XP - is that what your customer has? I don't think there is a workaround. According to Trend's documentation, signed executables should be OK but they don't seem to be. If you have any contacts at Trend I would ask them! Peter -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Get MSI logs when Burn chain failed
As I understand it, if you run the setup program from the command line with the /log filename option you will get a log from burn and then a separate file from the msi if it runs at all. If I get problems I usually try to install the bare msi first and then if that is OK I can assume it's something that burn is doing. Pete -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: Chain with MSI only packages fails with Directory not found error
Dear Henning,
I think this is the same problem I have seen and reported recently to this list:
http://sourceforge.net/mailarchive/forum.php?thread_name=DUB101-W57E6E77EDBB70153F4CD0CAD7C0%40phx.gblforum_name=wix-users
I think it really is a bug (the 3.6beta worked for me) so I will file one on
SF.net.
Peter
From: hkra...@infinitec.de
To: wix-users@lists.sourceforge.net
Date: Wed, 15 Feb 2012 09:03:14 +
Subject: [WiX-users] Burn: Chain with MSI only packages fails with Directory
not found error
I'm using WiX v3.6.2610.0
Test platform: Windows 2003 x86 en, latest service pack
I created a Burn Bootstrapper which installs one MSI as Per User. Depending
on the state of the target machine, some prereqs have to be installed
per-machine.
So I created this bootstrapper:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Bundle Name=Super product Version=1.0.0.0 Manufacturer=Someone
UpgradeCode=2F4ACE94-1117-4D3F-98E4-7DBA5EACC60E Compressed=yes
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.HyperlinkLicense /
WixVariable Id=WixStdbaLogo Value=AppIcon.bmp /
WixVariable Id=WixStdbaLicenseUrl Value=http://example.com/license.html;
/
util:RegistrySearch Key=SOFTWARE\Microsoft\VSTO Runtime Setup\v4R
Value=VSTORFeature_CLR40 Win64=no Variable=VSTO2010Present Root=HKLM/
Chain
ExePackage Name=VSTO 2010 x64
DetectCondition=VSTO2010Present=1 Compressed=no
InstallCommand=vstor40_x64.exe /q
DownloadUrl=http://download.microsoft.com/download/F/3/9/F395E3C2-28A0-4F0D-9E20-FF4D1ADB08D8/vstor40_x64.exe;
SourceFile=External Setups\vstor40_x64.exe
PerMachine=yes
UninstallCommand=vstor40_x64.exe /qu
Vital=yes Permanent=yes /
MsiPackage SourceFile=Installers\OutlookAddinX86.msi Name=Outlook addin
(x86) Cache=yes Compressed=yes /
/Chain
/Bundle
/Wix
Works like charm if the ExePackage needs to be installed as well. But if that
package is already installed, the setup fails:
[180C:1704][2012-02-15T09:58:18]: Burn v3.6.2610.0, path:
C:\Product\Development\UI\Build\Outlook Addin Setup\Bootstrapper.exe,
cmdline: ''
[180C:1704][2012-02-15T09:58:18]: Setting string variable 'WixBundleLog' to
value
'C:\Users\Administrator\AppData\Local\Temp\Super_product_20120215095818.log'
[180C:1704][2012-02-15T09:58:18]: Setting string variable 'WixBundleName' to
value 'Super product'
[180C:1704][2012-02-15T09:58:18]: Setting string variable
'WixBundleOriginalSource' to value 'C:\Product\Development\UI\Build\Outlook
Addin Setup\Bootstrapper.exe'
[180C:1704][2012-02-15T09:58:19]: Detect 2 packages
[180C:1704][2012-02-15T09:58:19]: Setting string variable 'VSTO2010Present'
to value '1'
[180C:1704][2012-02-15T09:58:19]: Condition 'VSTO2010Present=1' evaluates to
true.
[180C:1704][2012-02-15T09:58:19]: Detected package: VSTO_2010_x64, state:
Present, cached: No
[180C:1704][2012-02-15T09:58:19]: Detected package: Outlook_addin__x86_,
state: Absent, cached: No
[180C:1704][2012-02-15T09:58:19]: Detect complete, result: 0x0
[180C:1704][2012-02-15T09:58:22]: Plan 2 packages, action: Install
[180C:1704][2012-02-15T09:58:22]: Skipping dependency registration on package
with no dependency providers: VSTO_2010_x64
[180C:1704][2012-02-15T09:58:22]: Planned package: VSTO_2010_x64, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[180C:1704][2012-02-15T09:58:22]: Setting string variable
'WixBundleLog_Outlook_addin__x86_' to value
'C:\Users\Administrator\AppData\Local\Temp\Super_product_20120215095818_0_Outlook_addin__x86_.log'
[180C:1704][2012-02-15T09:58:22]: Setting string variable
'WixBundleRollbackLog_Outlook_addin__x86_' to value
'C:\Users\Administrator\AppData\Local\Temp\Super_product_20120215095818_0_Outlook_addin__x86__rollback.log'
[180C:1704][2012-02-15T09:58:22]: Planned package: Outlook_addin__x86_,
state: Absent, default requested: Present, ba requested: Present, execute:
Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[180C:1704][2012-02-15T09:58:22]: Plan complete, result: 0x0
[180C:1704][2012-02-15T09:58:22]: Apply begin
[180C:1704][2012-02-15T09:58:22]: Caching bundle from:
'C:\Users\Administrator\AppData\Local\Temp\1\{db0b8631-45f6-43e8-9c45-4dbf76a5a05d}\.be\Bootstrapper.exe'
to: 'C:\Users\Administrator\AppData\Local\Package
Cache\{db0b8631-45f6-43e8-9c45-4dbf76a5a05d}\Bootstrapper.exe'
[180C:1704][2012-02-15T09:58:22]: Error 0x80070003: Failed to cache bundle
from:
'C:\Users\Administrator\AppData\Local\Temp\1\{db0b8631-45f6-43e8-9c45-4dbf76a5a05d}\.be\Bootstrapper.exe'
to 'C:\Users\Administrator\AppData\Local\Package
Cache\{db0b8631-45f6-43e8-9c45-4dbf76a5a05d}\Bootstrapper.exe'
Re: [WiX-users] Burn: Chain with MSI only packages fails with Directory not found error
OK I have filed a bug:
https://sourceforge.net/tracker/?func=detailaid=3487838group_id=105970atid=642714
I've tried to include your information, please add/correct as appropriate.
Peter
From: hkra...@infinitec.de
To: wix-users@lists.sourceforge.net
Date: Wed, 15 Feb 2012 09:03:14 +
Subject: [WiX-users] Burn: Chain with MSI only packages fails with Directory
not found error
I'm using WiX v3.6.2610.0
Test platform: Windows 2003 x86 en, latest service pack
I created a Burn Bootstrapper which installs one MSI as Per User. Depending
on the state of the target machine, some prereqs have to be installed
per-machine.
So I created this bootstrapper:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Bundle Name=Super product Version=1.0.0.0 Manufacturer=Someone
UpgradeCode=2F4ACE94-1117-4D3F-98E4-7DBA5EACC60E Compressed=yes
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.HyperlinkLicense /
WixVariable Id=WixStdbaLogo Value=AppIcon.bmp /
WixVariable Id=WixStdbaLicenseUrl Value=http://example.com/license.html;
/
util:RegistrySearch Key=SOFTWARE\Microsoft\VSTO Runtime Setup\v4R
Value=VSTORFeature_CLR40 Win64=no Variable=VSTO2010Present Root=HKLM/
Chain
ExePackage Name=VSTO 2010 x64
DetectCondition=VSTO2010Present=1 Compressed=no
InstallCommand=vstor40_x64.exe /q
DownloadUrl=http://download.microsoft.com/download/F/3/9/F395E3C2-28A0-4F0D-9E20-FF4D1ADB08D8/vstor40_x64.exe;
SourceFile=External Setups\vstor40_x64.exe
PerMachine=yes
UninstallCommand=vstor40_x64.exe /qu
Vital=yes Permanent=yes /
MsiPackage SourceFile=Installers\OutlookAddinX86.msi Name=Outlook addin
(x86) Cache=yes Compressed=yes /
/Chain
/Bundle
/Wix
Works like charm if the ExePackage needs to be installed as well. But if that
package is already installed, the setup fails:
[180C:1704][2012-02-15T09:58:18]: Burn v3.6.2610.0, path:
C:\Product\Development\UI\Build\Outlook Addin Setup\Bootstrapper.exe,
cmdline: ''
[180C:1704][2012-02-15T09:58:18]: Setting string variable 'WixBundleLog' to
value
'C:\Users\Administrator\AppData\Local\Temp\Super_product_20120215095818.log'
[180C:1704][2012-02-15T09:58:18]: Setting string variable 'WixBundleName' to
value 'Super product'
[180C:1704][2012-02-15T09:58:18]: Setting string variable
'WixBundleOriginalSource' to value 'C:\Product\Development\UI\Build\Outlook
Addin Setup\Bootstrapper.exe'
[180C:1704][2012-02-15T09:58:19]: Detect 2 packages
[180C:1704][2012-02-15T09:58:19]: Setting string variable 'VSTO2010Present'
to value '1'
[180C:1704][2012-02-15T09:58:19]: Condition 'VSTO2010Present=1' evaluates to
true.
[180C:1704][2012-02-15T09:58:19]: Detected package: VSTO_2010_x64, state:
Present, cached: No
[180C:1704][2012-02-15T09:58:19]: Detected package: Outlook_addin__x86_,
state: Absent, cached: No
[180C:1704][2012-02-15T09:58:19]: Detect complete, result: 0x0
[180C:1704][2012-02-15T09:58:22]: Plan 2 packages, action: Install
[180C:1704][2012-02-15T09:58:22]: Skipping dependency registration on package
with no dependency providers: VSTO_2010_x64
[180C:1704][2012-02-15T09:58:22]: Planned package: VSTO_2010_x64, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[180C:1704][2012-02-15T09:58:22]: Setting string variable
'WixBundleLog_Outlook_addin__x86_' to value
'C:\Users\Administrator\AppData\Local\Temp\Super_product_20120215095818_0_Outlook_addin__x86_.log'
[180C:1704][2012-02-15T09:58:22]: Setting string variable
'WixBundleRollbackLog_Outlook_addin__x86_' to value
'C:\Users\Administrator\AppData\Local\Temp\Super_product_20120215095818_0_Outlook_addin__x86__rollback.log'
[180C:1704][2012-02-15T09:58:22]: Planned package: Outlook_addin__x86_,
state: Absent, default requested: Present, ba requested: Present, execute:
Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[180C:1704][2012-02-15T09:58:22]: Plan complete, result: 0x0
[180C:1704][2012-02-15T09:58:22]: Apply begin
[180C:1704][2012-02-15T09:58:22]: Caching bundle from:
'C:\Users\Administrator\AppData\Local\Temp\1\{db0b8631-45f6-43e8-9c45-4dbf76a5a05d}\.be\Bootstrapper.exe'
to: 'C:\Users\Administrator\AppData\Local\Package
Cache\{db0b8631-45f6-43e8-9c45-4dbf76a5a05d}\Bootstrapper.exe'
[180C:1704][2012-02-15T09:58:22]: Error 0x80070003: Failed to cache bundle
from:
'C:\Users\Administrator\AppData\Local\Temp\1\{db0b8631-45f6-43e8-9c45-4dbf76a5a05d}\.be\Bootstrapper.exe'
to 'C:\Users\Administrator\AppData\Local\Package
Cache\{db0b8631-45f6-43e8-9c45-4dbf76a5a05d}\Bootstrapper.exe'
[180C:1704][2012-02-15T09:58:22]: Error 0x80070003: Failed to cache bundle
from path:
Re: [WiX-users] Very simplest bundle not working
I've done a bit of playing around and it seems to be linked to install conditions, i.e. if I change my bundle's chain to Chain MsiPackage Id=one SourceFile=install.msi Compressed=yes InstallCondition= 1 / MsiPackage Id=two SourceFile=install.msi Compressed=yes InstallCondition= NOT 1 / /Chain it works, even with these 'silly' conditions. Date: Wed, 15 Feb 2012 10:43:09 -0500 From: b...@joyofsetup.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Very simplest bundle not working On 15-Feb-12 10:15, Rob Mensching wrote: File a bug, but I'm not exactly sure how to investigate. I'm (obviously) not seeing the same problem. And if you're installing the WiX toolset, then you aren't either (at least once).smile/ Both bugs involve per-user packages... -- sig://boB http://joyofsetup.com/ -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Very simplest bundle not working
Actually that turned out to be a red herring. I think the real cause is (as you suspected) the InstallScope. I only see the error for perUser MSI packages. I am using WinXP so maybe that is why you can't reproduce it?I appreciate your help on this, thanks.Pete Date: Wed, 15 Feb 2012 14:30:41 -0500 From: b...@joyofsetup.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Very simplest bundle not working Please add that to the bug... On 15-Feb-12 11:57, Peter Hull wrote: I've done a bit of playing around and it seems to be linked to install conditions, i.e. if I change my bundle's chain to Chain MsiPackage Id=one SourceFile=install.msi Compressed=yes InstallCondition= 1 / MsiPackage Id=two SourceFile=install.msi Compressed=yes InstallCondition= NOT 1 / /Chain it works, even with these 'silly' conditions. -- sig://boB http://joyofsetup.com/ -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Very simplest bundle not working
I've rechecked and it works fine on the beta version (build 2221 I think) - so
is this a regression or have I made a mistake in my wxs file?
I would appreciate it if someone could have a quick check of this for me. Or
should I file a bug?
Thanks,Pete
From: peterhul...@hotmail.com
To: wix-users@lists.sourceforge.net
Date: Sat, 11 Feb 2012 11:54:09 +
Subject: Re: [WiX-users] Very simplest bundle not working
Hotmail ruined my message! Trying again..
Dear All,
I've made quite a few installers and bundles with WiX already, but all of a
sudden when making a minimal example, I can't seem to get it to work! Please
can you have a look, I'm sure I must be doing something obviously wrong. This
is WiX 3.6.2603.0 on WinXP.
I've got a wxs to make an empty MSI:
Version='1.0.0.0' Manufacturer='PH'
UpgradeCode='{4542D2F4-147B-4F37-88F9-2C2FB1347328}'
Comments='A single file'
Manufacturer='PH' InstallerVersion='200' Compressed='yes'
InstallScope=perUser /
Then a second wxs to make the bundle:
And I am building like this:
candle install.wxs
candle bundle.wxs
light install.wixobj
light bundle.wixobj -ext WixBalExtension
It compiles OK but when I run I get error 0x8007003 (File Not Found) with the
following log:
[0A94:08FC][2012-02-11T10:02:55]: Burn v3.6.2603.0, path: C:\Documents and
Settings\peter hull.UKDEEDEV012\My Documents\minimal\bundle.exe, cmdline: '/q
/log install.txt'
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable 'WixBundleLog' to
value 'C:\Documents and Settings\peter hull.UKDEEDEV012\My
Documents\minimal\install.txt'
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable 'WixBundleName' to
value ''
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable
'WixBundleOriginalSource' to value 'C:\Documents and Settings\peter
hull.UKDEEDEV012\My Documents\minimal\bundle.exe'
[0A94:08FC][2012-02-11T10:02:55]: Detect 1 packages
[0A94:08FC][2012-02-11T10:02:55]: Detected package: install.msi, state:
Absent, cached: No
[0A94:08FC][2012-02-11T10:02:55]: Detect complete, result: 0x0
[0A94:08FC][2012-02-11T10:02:55]: Plan 1 packages, action: Install
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable
'WixBundleLog_install.msi' to value 'C:\Documents and Settings\peter
hull.UKDEEDEV012\My Documents\minimal\install_0_install.msi.txt'
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable
'WixBundleRollbackLog_install.msi' to value 'C:\Documents and Settings\peter
hull.UKDEEDEV012\My Documents\minimal\install_0_install.msi_rollback.txt'
[0A94:08FC][2012-02-11T10:02:55]: Planned package: install.msi, state:
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0A94:08FC][2012-02-11T10:02:55]: Plan complete, result: 0x0
[0A94:08FC][2012-02-11T10:02:55]: Apply begin
[0A94:08FC][2012-02-11T10:02:55]: Caching bundle from:
'C:\DOCUME~1\PETERH~1.UKD\LOCALS~1\Temp\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\.be\bundle.exe'
to: 'C:\Documents and Settings\peter hull.UKDEEDEV012\Local
Settings\Application Data\Package
Cache\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\bundle.exe'
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to cache bundle
from:
'C:\DOCUME~1\PETERH~1.UKD\LOCALS~1\Temp\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\.be\bundle.exe'
to 'C:\Documents and Settings\peter hull.UKDEEDEV012\Local
Settings\Application Data\Package
Cache\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\bundle.exe'
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to cache bundle
from path:
C:\DOCUME~1\PETERH~1.UKD\LOCALS~1\Temp\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\.be\bundle.exe
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to begin
registration session.
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to register bundle.
[0A94:08FC][2012-02-11T10:02:55]: Apply complete, result: 0x80070003 restart:
No
[0A94:08FC][2012-02-11T10:02:55]: Shutting down, exit code: 0x80070003
Any ideas?
Pete
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you
[WiX-users] Very simplest bundle not working
Dear All,
I've made quite a few installers and bundles with WiX already, but all of a
sudden when making a minimal example, I can't seem to get it to work! Please
can you have a look, I'm sure I must be doing something obviously wrong. This
is WiX 3.6.2603.0 on WinXP.
I've got a wxs to make an empty MSI:
Then a second wxs to make the bundle:
And I am building like this:
candle install.wxs
candle bundle.wxs
light install.wixobj
light bundle.wixobj -ext WixBalExtension
It compiles OK but when I run I get error 0x8007003 (File Not Found) with the
following log:
[0A94:08FC][2012-02-11T10:02:55]: Burn v3.6.2603.0, path: C:\Documents and
Settings\peter hull.UKDEEDEV012\My Documents\minimal\bundle.exe, cmdline: '/q
/log install.txt'
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable 'WixBundleLog' to
value 'C:\Documents and Settings\peter hull.UKDEEDEV012\My
Documents\minimal\install.txt'
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable 'WixBundleName' to
value ''
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable
'WixBundleOriginalSource' to value 'C:\Documents and Settings\peter
hull.UKDEEDEV012\My Documents\minimal\bundle.exe'
[0A94:08FC][2012-02-11T10:02:55]: Detect 1 packages
[0A94:08FC][2012-02-11T10:02:55]: Detected package: install.msi, state: Absent,
cached: No
[0A94:08FC][2012-02-11T10:02:55]: Detect complete, result: 0x0
[0A94:08FC][2012-02-11T10:02:55]: Plan 1 packages, action: Install
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable
'WixBundleLog_install.msi' to value 'C:\Documents and Settings\peter
hull.UKDEEDEV012\My Documents\minimal\install_0_install.msi.txt'
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable
'WixBundleRollbackLog_install.msi' to value 'C:\Documents and Settings\peter
hull.UKDEEDEV012\My Documents\minimal\install_0_install.msi_rollback.txt'
[0A94:08FC][2012-02-11T10:02:55]: Planned package: install.msi, state: Absent,
default requested: Present, ba requested: Present, execute: Install, rollback:
Uninstall, cache: Yes, uncache: No, dependency: Register
[0A94:08FC][2012-02-11T10:02:55]: Plan complete, result: 0x0
[0A94:08FC][2012-02-11T10:02:55]: Apply begin
[0A94:08FC][2012-02-11T10:02:55]: Caching bundle from:
'C:\DOCUME~1\PETERH~1.UKD\LOCALS~1\Temp\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\.be\bundle.exe'
to: 'C:\Documents and Settings\peter hull.UKDEEDEV012\Local
Settings\Application Data\Package
Cache\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\bundle.exe'
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to cache bundle
from:
'C:\DOCUME~1\PETERH~1.UKD\LOCALS~1\Temp\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\.be\bundle.exe'
to 'C:\Documents and Settings\peter hull.UKDEEDEV012\Local
Settings\Application Data\Package
Cache\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\bundle.exe'
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to cache bundle from
path:
C:\DOCUME~1\PETERH~1.UKD\LOCALS~1\Temp\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\.be\bundle.exe
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to begin
registration session.
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to register bundle.
[0A94:08FC][2012-02-11T10:02:55]: Apply complete, result: 0x80070003 restart: No
[0A94:08FC][2012-02-11T10:02:55]: Shutting down, exit code: 0x80070003
Any ideas?
Pete
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Very simplest bundle not working
Hotmail ruined my message! Trying again..
Dear All,
I've made quite a few installers and bundles with WiX already, but all of a
sudden when making a minimal example, I can't seem to get it to work! Please
can you have a look, I'm sure I must be doing something obviously wrong. This
is WiX 3.6.2603.0 on WinXP.
I've got a wxs to make an empty MSI:
?xml version='1.0'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
Product Id='{4C2E4CA4-F8A9-456D-AD1F-5264D3A2B0F1}' Name='Test Package'
Language='1033'
Version='1.0.0.0' Manufacturer='PH'
UpgradeCode='{4542D2F4-147B-4F37-88F9-2C2FB1347328}'
Package Description='Dummy package'
Comments='A single file'
Manufacturer='PH' InstallerVersion='200' Compressed='yes'
InstallScope=perUser /
Directory Id='TARGETDIR' Name='SourceDir'
Component Id='MyComponent' Guid={898E4A4A-DF56-45F2-BE76-56CE109BCA82}
/Component
/Directory
Feature Id='MyFeature' Title='My 1st Feature' Level='1'
ComponentRef Id='MyComponent' /
/Feature
/Product
/Wix
Then a second wxs to make the bundle:
?xml version=1.0?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Bundle Version=1.0.0.0
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense /
Chain
MsiPackage SourceFile=install.msi Compressed=yes /
/Chain
/Bundle
/Wix
And I am building like this:
candle install.wxs
candle bundle.wxs
light install.wixobj
light bundle.wixobj -ext WixBalExtension
It compiles OK but when I run I get error 0x8007003 (File Not Found) with the
following log:
[0A94:08FC][2012-02-11T10:02:55]: Burn v3.6.2603.0, path: C:\Documents and
Settings\peter hull.UKDEEDEV012\My Documents\minimal\bundle.exe, cmdline: '/q
/log install.txt'
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable 'WixBundleLog' to
value 'C:\Documents and Settings\peter hull.UKDEEDEV012\My
Documents\minimal\install.txt'
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable 'WixBundleName' to
value ''
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable
'WixBundleOriginalSource' to value 'C:\Documents and Settings\peter
hull.UKDEEDEV012\My Documents\minimal\bundle.exe'
[0A94:08FC][2012-02-11T10:02:55]: Detect 1 packages
[0A94:08FC][2012-02-11T10:02:55]: Detected package: install.msi, state: Absent,
cached: No
[0A94:08FC][2012-02-11T10:02:55]: Detect complete, result: 0x0
[0A94:08FC][2012-02-11T10:02:55]: Plan 1 packages, action: Install
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable
'WixBundleLog_install.msi' to value 'C:\Documents and Settings\peter
hull.UKDEEDEV012\My Documents\minimal\install_0_install.msi.txt'
[0A94:08FC][2012-02-11T10:02:55]: Setting string variable
'WixBundleRollbackLog_install.msi' to value 'C:\Documents and Settings\peter
hull.UKDEEDEV012\My Documents\minimal\install_0_install.msi_rollback.txt'
[0A94:08FC][2012-02-11T10:02:55]: Planned package: install.msi, state: Absent,
default requested: Present, ba requested: Present, execute: Install, rollback:
Uninstall, cache: Yes, uncache: No, dependency: Register
[0A94:08FC][2012-02-11T10:02:55]: Plan complete, result: 0x0
[0A94:08FC][2012-02-11T10:02:55]: Apply begin
[0A94:08FC][2012-02-11T10:02:55]: Caching bundle from:
'C:\DOCUME~1\PETERH~1.UKD\LOCALS~1\Temp\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\.be\bundle.exe'
to: 'C:\Documents and Settings\peter hull.UKDEEDEV012\Local
Settings\Application Data\Package
Cache\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\bundle.exe'
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to cache bundle
from:
'C:\DOCUME~1\PETERH~1.UKD\LOCALS~1\Temp\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\.be\bundle.exe'
to 'C:\Documents and Settings\peter hull.UKDEEDEV012\Local
Settings\Application Data\Package
Cache\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\bundle.exe'
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to cache bundle from
path:
C:\DOCUME~1\PETERH~1.UKD\LOCALS~1\Temp\{98c3a113-6f9a-4c5f-a6d3-b1da166bbbe6}\.be\bundle.exe
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to begin
registration session.
[0A94:08FC][2012-02-11T10:02:55]: Error 0x80070003: Failed to register bundle.
[0A94:08FC][2012-02-11T10:02:55]: Apply complete, result: 0x80070003 restart: No
[0A94:08FC][2012-02-11T10:02:55]: Shutting down, exit code: 0x80070003
Any ideas?
Pete
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] standard bootstapper and non-admin user
The message is
0x8007051b - This security ID maynot be assigned as the owner of this object.
Here's the log:
[12B8:12F8][2012-02-06T14:21:24]: Burn v3.6.2527.0, path: C:\Users\Peter
Hull\Documents\in2it System Software\Setup.exe, cmdline: ''
[12B8:12F8][2012-02-06T14:21:25]: Setting string variable 'WixBundleLog' to
value
'C:\Users\PETERH~1\AppData\Local\Temp\in2it_System_Software_20120206142125.log'
[12B8:12F8][2012-02-06T14:21:25]: Setting string variable 'WixBundleName' to
value '...'
[12B8:12F8][2012-02-06T14:21:25]: Setting string variable
'WixBundleOriginalSource' to value 'C:\Users\Peter Hull\Documents\...\Setup.exe'
[12B8:12F8][2012-02-06T14:21:25]: Detect 2 packages
[12B8:12F8][2012-02-06T14:21:25]: Detected package: setup32.msi, state: Absent,
cached: No
[12B8:12F8][2012-02-06T14:21:25]: Detected package: setup64.msi, state: Absent,
cached: No
[12B8:12F8][2012-02-06T14:21:25]: Detect complete, result: 0x0
[12B8:12F8][2012-02-06T14:21:29]: Plan 2 packages, action: Install
[12B8:12F8][2012-02-06T14:21:29]: Condition 'Not VersionNT64' evaluates to
false.
[12B8:12F8][2012-02-06T14:21:29]: Planned package: setup32.msi, state: Absent,
default requested: Absent, ba requested: Absent, execute: None, rollback: None,
cache: No, uncache: No, dependency: None
[12B8:12F8][2012-02-06T14:21:29]: Condition 'VersionNT64' evaluates to true.
[12B8:12F8][2012-02-06T14:21:29]: Setting string variable
'WixBundleLog_setup64.msi' to value
'C:\Users\PETERH~1\AppData\Local\Temp\..._20120206142125_0_setup64.msi.log'
[12B8:12F8][2012-02-06T14:21:29]: Setting string variable
'WixBundleRollbackLog_setup64.msi' to value
'C:\Users\PETERH~1\AppData\Local\Temp\..._20120206142125_0_setup64.msi_rollback.log'
[12B8:12F8][2012-02-06T14:21:29]: Planned package: setup64.msi, state: Absent,
default requested: Present, ba requested: Present, execute: Install, rollback:
Uninstall, cache: Yes, uncache: No, dependency: Register
[12B8:12F8][2012-02-06T14:21:29]: Plan complete, result: 0x0
[12B8:12F8][2012-02-06T14:21:29]: Apply begin
[04D4:0DC8][2012-02-06T14:21:35]: Error 0x8007051b: Failed to secure cache
path: C:\ProgramData\Package Cache\
[04D4:0DC8][2012-02-06T14:21:35]: Error 0x8007051b: Failed to secure cache
directory: C:\ProgramData\Package Cache\
[04D4:0DC8][2012-02-06T14:21:35]: Error 0x8007051b: Failed to create completed
cache path for bundle.
[04D4:0DC8][2012-02-06T14:21:35]: Error 0x8007051b: Failed to cache bundle from
path:
C:\Users\PETERH~1\AppData\Local\Temp\{a477d6ef-5c9f-4330-9058-8bb42e84fa85}\.be\Setup.exe
[04D4:0DC8][2012-02-06T14:21:35]: Error 0x8007051b: Failed to begin
registration session.
[12B8:12F8][2012-02-06T14:21:35]: Error 0x8007051b: Failed to begin
registration session in per-machine process.
[12B8:12F8][2012-02-06T14:21:35]: Error 0x8007051b: Failed to register bundle.
[12B8:12F8][2012-02-06T14:21:35]: Apply complete, result: 0x8007051b restart: No
From: peterhul...@hotmail.com
To: wix-users@lists.sourceforge.net
Date: Sat, 4 Feb 2012 09:36:09 +
Subject: Re: [WiX-users] standard bootstapper and non-admin user
I've got 2 MSIs, both with in their package element, and the bundle's wxs
looks like this:
?xml version=1.0?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Bundle Version=... Name=...
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplicat\ion.RtfLicense /
WixVariable Id=WixStdbaLicenseRtf Value= /
WixVariable Id=WixStdbaLogo Value=… /
Chain
MsiPackage SourceFile=obj\setup32.msi Compressed=ye\s
InstallCondition=Not VersionNT64 /
MsiPackage SourceFile=obj\setup64.msi Compressed=ye\s
InstallCondition=VersionNT64 /
/Chain
/Bundle
/Wix
I haven't got access to the system right now but it's windows 7 64-bit
enterprise and the user is not an admin. The error message is something about
not being able to use the token (I will write down exactly what on Monday)
Pete
From: r...@robmensching.com
Date: Fri, 3 Feb 2012 23:18:28 -0800
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] standard bootstapper and non-admin user
How did you mark that your MSIs are per-machine? The best thing to use is
the Package/@InstallScope attribute. Burn should automatically prompt for
elevation if it determines your MSIs are per-machine.
On Fri, Feb 3, 2012 at 12:21 AM, Peter Hull peterhul...@hotmail.com wrote:
I've made an installer for 32- and 64-bit windows with separate MSIs,
bundled with the standard BA
(WixStandardBootstrapperApplication.RtfLicense). Both MSIs need admin
privileges and are marked per-machine. If I run the installer as a
non-admin user, the error message that the setup program gives is quite
technical and (T believe) not all that helpful to the end user. Is there
any way to make this message more friendly? In the MSI authoring I have
been using something like Condition Message=...Privileged/Condition
Re: [WiX-users] standard bootstapper and non-admin user
I've got 2 MSIs, both with in their package element, and the bundle's wxs looks like this:?xml version=1.0?Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Version=... Name=... BootstrapperApplicationRef Id=WixStandardBootstrapperApplicat\ion.RtfLicense / WixVariable Id=WixStdbaLicenseRtf Value= / WixVariable Id=WixStdbaLogo Value=… / Chain MsiPackage SourceFile=obj\setup32.msi Compressed=ye\s InstallCondition=Not VersionNT64 / MsiPackage SourceFile=obj\setup64.msi Compressed=ye\s InstallCondition=VersionNT64 / /Chain /Bundle/Wix I haven't got access to the system right now but it's windows 7 64-bit enterprise and the user is not an admin. The error message is something about not being able to use the token (I will write down exactly what on Monday) Pete From: r...@robmensching.com Date: Fri, 3 Feb 2012 23:18:28 -0800 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] standard bootstapper and non-admin user How did you mark that your MSIs are per-machine? The best thing to use is the Package/@InstallScope attribute. Burn should automatically prompt for elevation if it determines your MSIs are per-machine. On Fri, Feb 3, 2012 at 12:21 AM, Peter Hull peterhul...@hotmail.com wrote: I've made an installer for 32- and 64-bit windows with separate MSIs, bundled with the standard BA (WixStandardBootstrapperApplication.RtfLicense). Both MSIs need admin privileges and are marked per-machine. If I run the installer as a non-admin user, the error message that the setup program gives is quite technical and (T believe) not all that helpful to the end user. Is there any way to make this message more friendly? In the MSI authoring I have been using something like Condition Message=...Privileged/Condition. Is there an equivalent? Alternatively, would it make sense to mark the exe as requiresAdministrator in the manifest? Pete -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] standard bootstapper and non-admin user
I've made an installer for 32- and 64-bit windows with separate MSIs, bundled with the standard BA (WixStandardBootstrapperApplication.RtfLicense). Both MSIs need admin privileges and are marked per-machine. If I run the installer as a non-admin user, the error message that the setup program gives is quite technical and (T believe) not all that helpful to the end user. Is there any way to make this message more friendly? In the MSI authoring I have been using something like Condition Message=...Privileged/Condition. Is there an equivalent? Alternatively, would it make sense to mark the exe as requiresAdministrator in the manifest? Pete -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Install issue - wix2010.target line 761
The location of the exes is taken from the registry and put in $(WixToolPath). Can you check the InstallRoot value under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Installer XML\3.5 or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Installer XML\3.5 and see if it is correct? Otherwise, are you overriding $(WixToolPath) somewhere else in the project? Pete Date: Wed, 1 Feb 2012 22:56:52 + From: mark.sug...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Install issue - wix2010.target line 761 Thanks for the reply. How do I set %WIX%? And what should I set it to? Previously, I just installed WiX and compile worked fine. What might have changed? On Wed, Feb 1, 2012 at 18:05, Blair os...@live.com wrote: I don't know. Is the %WIX% environment variable set? I use the HarvestDirectory items instead of the PreBuildEvent property to use the harvester in 3.5 myself. -Original Message- From: Mark Sugrue [mailto:mark.sug...@gmail.com] Sent: Wednesday, February 01, 2012 8:57 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Install issue - wix2010.target line 761 I'm setting up a new build machine. VS2010, Wix3.5, etc. Everything the same as the old machine. (both are x64 Win7 Pro) When I try to build the installer on the new machine, I get an odd error which I don't understand. Nothing on the web seems to match it. The error isn't in my code, its on line 761 of wix2010.targets The line is Exec WorkingDirectory=$(OutDir) Command=$(ExpandedPreBuildEvent) / I haven't edited this file at all. The error I get is this: Error 3 The command %WIX%\bin\heat dir D:\Code\products\LE\bin\Debug\Help -dr HelpFolder -cg HelpComponentGroup -var var.HelpDir -srd -gg -sfrag -suid -template:fragment -out D:\Code\products\LE\Setup\help.wxs.sample exited with code 3. C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.x\wix2010.targets761 6 Setup But the exact same code compiles fine on the old machine. Is there some setting I need to change maybe? -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Weekly Builds?
Is there any chance you could put a date and/or a changeset number by each release so we can see easily what's new in each one? Thanks, Pete -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] When install exe built with burn, UAC dialog says Unknown Publisher
Did you override the targets *after* Import Project=$(WixTargetsPath) / (I'm just saying because this caught me out.) Pete From: scott.lang...@appsense.com To: wix-users@lists.sourceforge.net Date: Tue, 24 Jan 2012 10:11:19 + Subject: Re: [WiX-users] When install exe built with burn, UAC dialog says Unknown Publisher I invoked MSBuild with the build project command from within the VS2010 IDE. To try and check if we've missed signing anything I added overrides of the SignXXX targets into our project file. In the overrides, I added WriteLinesToFile tasks to dump out the @(SignXXX) item groups. I didn't get any files output from the SignXXX tasks. To test I had the WriteLinesToFile working correctly, I did manage to dump out files out from overridden BeforeBuild and AfterBuild targets. I think burn.exe is the latest, it says it's version 3.6.2221.0 -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: 24 January 2012 02:56 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] When install exe built with burn, UAC dialog says Unknown Publisher On 23-Jan-12 10:29, scott.lang...@appsense.com wrote: And tried to override the Signxxx targets, but as far as I can tell, they don't get called. How did you invoke MSBuild? -- sig://boB http://joyofsetup.com/ -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This email and all attachments are CONFIDENTIAL. It is meant for the intended recipient(s) only. If you are not the intended recipient(s), please notify the sender immediately and delete this email and any attachment; you must not disclose the contents to any other person or make any copies. We may monitor email communications to the extent permitted or as required by law and as necessary and justifiable for business purposes. This email and its contents (including, without limitation, quotes) shall not operate to bind AppSense to any order or contract unless expressly confirmed in writing by AppSense. AppSense Limited is a limited company registered in England and Wales (company number 3873980) and its registered office address is at 3300 Daresbury Business Park,Daresbury,Warrington, WA4 4HS, UK -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] difx extension and perMachine installs
If the driver is not signed, and you say it is not, then you need the Legacy option. I did say that; what I meant was not signed with a certificate from a CA. It is self-signed at the moment. Apologies for the confusion. I'd still like to hear if anyone has any comments on a per-user install which includes a device driver - is it always better to do it per-machine. Pete -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing the burn bootstrapper
From: b...@joyofsetup.com On 13-Jan-12 01:41, Peter Hull wrote: Bob: would it be possible to have the burn engine signed (by Microsoft) in the released WiX 3.6 That would mean that the UAC prompt would show Microsoft as the owner of your bundle. OK, I had thought the UAC prompt would come from the 'outer' bundle executable - but I realise now why that wouldn't make sense! or have an option to specify the burn engine in the .wxs file - as I understand it you currently have to sign the burn engine every time the bundle is built, even though it's the same executable. If that's a concern, you can replace the burn.exe in bin\x86 in your WiX drop. Yes that would be an option though doing it in the .wxs would be better I think. Thanks, Pete -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] difx extension and perMachine installs
I am building an installer with a device driver, to be installed with the WiX difx extension. The driver is self-signed for testing purposes. I set my Package element to Package Description=... InstallerVersion=200 InstallScope=perUser Compressed=yes InstallPrivileges=elevated / and everything seemed fine. However I reasoned that a device driver had better be perMachine so I changed the InstallScope to perMachine. Now the installer fails and rolls back. Looking at the logs it is difx, returning error TRUST_E_NOSIGNATURE. My questions: 1. Does WiX handle the case where a perUser install has a device driver (as long as InstallPrivileges is elevated)? 2. Am I correct in saying that the problem is my self-signed certificate - it's trusted by 'me' but for a perMachine install it is no longer trusted? Thanks in advance, Pete -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] difx extension and perMachine installs
Thanks James, good point. The driver will be signed for production; it just isn't at the moment. I shouldn't need the Legacy option. I've been mulling over perUser vs. perMachine installs and my conclusion is that there's no point in a per-user install because the user would need to be an admin anyway (or be elevated) to install the driver. So I was a bit surprised when my per-machine installer failed but I _think_ it's because of where I put my self-signed certificate (in the user store, not the machine store) - I just want to be sure that I'm not missing something and the install won't fail in the field, and you guys are the experts! ThanksPete From: johnst...@inn-soft.com To: wix-users@lists.sourceforge.net Date: Mon, 16 Jan 2012 19:29:41 + Subject: Re: [WiX-users] difx extension and perMachine installs Did you remember to set the Legacy attribute to yes on your Driver element? See http://wix.sourceforge.net/manual-wix3/difxapp_xsd_driver.htm for more info. Specifically: Legacy YesNoType If set to yes, configures DIFxApp to install unsigned driver packages and driver packages with missing files Also see http://msdn.microsoft.com/en-us/library/ff547653(VS.85).aspx for more info on what legacy mode is. James -Original Message- From: Peter Hull [mailto:peterhul...@hotmail.com] Sent: Monday, January 16, 2012 14:59 To: WiX Users Subject: [WiX-users] difx extension and perMachine installs I am building an installer with a device driver, to be installed with the WiX difx extension. The driver is self-signed for testing purposes. I set my Package element to Package Description=... InstallerVersion=200 InstallScope=perUser Compressed=yes InstallPrivileges=elevated / and everything seemed fine. However I reasoned that a device driver had better be perMachine so I changed the InstallScope to perMachine. Now the installer fails and rolls back. Looking at the logs it is difx, returning error TRUST_E_NOSIGNATURE. My questions: 1. Does WiX handle the case where a perUser install has a device driver (as long as InstallPrivileges is elevated)? 2. Am I correct in saying that the problem is my self-signed certificate - it's trusted by 'me' but for a perMachine install it is no longer trusted? Thanks in advance, Pete -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reopen Burn triggers virus checker - ID: 3431068
I've used an old (2004?) version of InstallShield and it generated a setup.exe and the msi separately. I'm assuming that setup.exe is their bootstrapper and was well-known enough to go onto the AV makers white-lists. When burn is released hopefully its engine could also be white-listed, assuming it's always the same. As Rob said, some big products like Visual Studio will be using it. For now it seems that Nikolaj's attempts to get in touch with Trend have not been successful - maybe an approach from someone actually on the WiX team would bear fruit? Pete -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reopen Burn triggers virus checker - ID: 3431068
From: r...@robmensching.com We'll need to teach this anti-virus program about Burn. Fortunately big programs, like Visual Studio, are using Burn and if it kills them I hope we can muster some change. So are you saying we need to raise this as an issue with Trend Micro? Is the program that actually writes the registry always the same? (I'm a bit confused about what the stages are when a burn exe is run, particularly what the burn engine is and what the burn agent is) Pete -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing the burn bootstrapper
To sign the bundle and bundle engine you need to add the following to your .wixproj: Add SignOutputtrue/SignOutput to a PropertyGroup Implement the targets like this: Target Name=SignBundleEngine SignFile TimestampUrl=... CertificateThumbprint=... SigningTarget=@(SignBundleEngine) / /Target Target Name=SignBundle SignFile TimestampUrl=... CertificateThumbprint=... SigningTarget=@(SignBundle) / /Target You need to put these _after_ the Import Project=$(WixTargetsPath) / Alternatively you can use Exec Command='signtool.exe sign ...' / for more control. There is also a SignContainers target but I don't know quite what it does. When buiding MSIs, to sign them you need to implement Target Name=SignMsi If you have external CABs then also implement Target Name=SignCabs The things you need to sign are in an itemgroup with the same name as the target (e.g. @(SignMsi)) Note that you can't use the SignFile task for this, as it will only sign exes and dlls. You have to use Exec Command=signtool sign ... / Hope that helps, Pete -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Insignia in 3.6
From: r...@robmensching.com Date: Wed, 11 Jan 2012 07:55:13 -0800 That looks right. Please file a bug if the command-line help wasn't helpful. OK, bug 3472564. I've also attached a patch to the bug report - hopefully you can use it as a starting point at least. Pete -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Signing the burn bootstrapper
Signing only the bundle would prove that it came from your organisation and hadn't been tampered with - would that be enough? When run it would unpack the unsigned burn engine and the unsigned MSIs. Does anyone know if that would show the user a warning (or multiple warnings?) Bob: would it be possible to have the burn engine signed (by Microsoft) in the released WiX 3.6 or have an option to specify the burn engine in the .wxs file - as I understand it you currently have to sign the burn engine every time the bundle is built, even though it's the same executable. Pete -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reopen Burn triggers virus checker - ID: 3431068
Date: Thu, 12 Jan 2012 20:56:15 +0100 From: n...@panorama9.com I would start by digitally signing your burn bundle. The bundle is already signed with a Thawte code signing certificate The reported file name looks more like it's the extracted engine than your bundle itself. Have you signed the engine. Either should Trend Micro change there detection mechanism regarding the RunOnce key or the bundling framework of burn should change its default behavior . From the Trend docs I saw it seemed to suggest that 'Malware Behaviour Monitoring' could be turned off (indeed, terminating programs like this was not the default) and also that signed executables were exempt. So it maybe is a bug in Trend that means it doesn't work as documented? The other thing is that other installers (InstallShield) don't seem to do this so does anyone understand how InstallShield handles the reboot issue? Pete -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reopen Burn triggers virus checker - ID: 3431068
Hi Nikolaj!
Could you comment on whether your installer was signed (the bundle and the
actual engine which is unpacked out of it - see this link
https://sourceforge.net/mailarchive/forum.php?thread_name=CAHdHTVc1c2h3QuYsiXWcR8A1Xtk38Z3W2KCyAvuP3hMjYqKAiA%40mail.gmail.comforum_name=wix-users
)
I'm glad someone else has seen this problem, especially as you have more
control over your environment than I do!
Peter
Date: Wed, 11 Jan 2012 12:16:37 +0100
From: n...@panorama9.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Reopen Burn triggers virus checker - ID: 3431068
We have built a EXE with Wix 3.6 beta which are detected by Trend Micro
as Malware behavior and
we are looking for the reason for this.
This is the log entry from Trend Micro
---
Malware behavior blocking Terminate Registry High
C:\Documents and Settings\administrator.ADTEST\Local
Settings\Temp\{044fc46d-90ff-4769-9c96-28a774dcbd7a}\.be\copy-yvxrlsay.iz2-P9Agent.exe
Write
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\{044fc46d-90ff-4769-9c96-28a774dcbd7a}
---
Snip from previous case:
---
Burn-based installers trigger Trend OfficeScan (v.10.5) when they write
to the RunOnce registry key.
The virus checker terminates the installer immediately.
---
We have a complete testing enviroment where we can tweak, monitor and
reproduce this error and are more than
willing to assist in debugging this issue.
Please let me know anything we can provide to debug and solve this
Regards
Nikolaj Steensgaard
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Insignia in 3.6
Am I right to say that the documentation for the insignia tool is a bit out of date in the 3.6 beta? The output from insignia /? doesn't mention the options -ab, -ib or -im. Is the following correct usage? - To inscribe a database installer.msi with external cabs: 1. Sign the cabs 2. insignia -im installer.msi 3. Sign installer.msi - To sign a bundle setup.exe 1. insignia -ib setup.exe -o tmp.exe 2. Sign tmp.exe 3. insignia -ab tmp.exe setup.exe -o setup.exe 4. Sign setup.exe Thanks for your help, Pete -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.6 beta and virus checker
Can you open a bug with this information in it? I'm not exactly sure what we'll do about it but we should at least track the issue. Yes I will do when I'm back in work. I am a bit surprised nobody has seen this; I would have thought that there would be many other corporate users with Trend OfficeScan and a similar config. Done (bug #3431068, http://sourceforge.net/tracker/?func=detailaid=3431068group_id=105970atid=642714) I wrote my own program to make a similar change in the registry and nothing happened, so I'm not sure why the burn engine 'provokes' Trend in that way. Pete -- RSA#174; Conference 2012 Save $700 by Nov 18 Register now#33; 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 beta and virus checker
Dear All,
I am not able to install the new 3.6 beta exe file (Wix36.exe) because my virus
checker (Trend Micro OfficeScan) terminates the installer when it tries to
write to the RunOnce registry key.
I was able to download and run WiX 3.6 from the wix36-binaries.zip archive,
however my minimal test installer also falls foul of Trend for the same reason.
(I include my .wxs files below)
I've never seen this for any other package I've installed. Does anyone know
about this or have a workaround?
Peter
bfirst.wxs
==
?xml version=1.0?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Bundle Version=1.0 Name=First Wix 3.6
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense /
Chain
MsiPackage SourceFile=first.msi /
/Chain
/Bundle
/Wix
first.wxs
=
?xml version='1.0'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
Product Id='{1427C75A-90A8-46e4-B0A7-1BBA7DEEF0F3}' Name='Test Package'
Language='1033'
Version='1.0.0.0' Manufacturer='Microsoft Corporation'
UpgradeCode='{1DF5EE00-3C58-4a94-B57C-63AC18E85A6F}'
Package Description='My first Windows Installer package'
Comments='This is my first attempt at creating a Windows
Installer database'
Manufacturer='Microsoft Corporation' InstallerVersion='200'
Compressed='yes' /
Directory Id='TARGETDIR' Name='SourceDir'
Component Id='MyComponent'
Guid='{87D198BF-6B84-4bd8-811E-8831A89FC721}' /
/Directory
Feature Id='MyFeature' Title='My 1st Feature' Level='1'
ComponentRef Id='MyComponent' /
/Feature
/Product
/Wix
--
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 3.6 beta and virus checker
From: r...@robmensching.com Date: Tue, 25 Oct 2011 08:26:40 -0700 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX 3.6 beta and virus checker Wow, that's a pretty aggressive virus checker. How do you install software that requires a reboot with that thing turned on? It's my work system so I don't have access to/can't change the policies it is using. I've installed loads of things in the past based on InstallShield, InnoSetup etc, and never seen this error message. I can't remember if any of them required a reboot but I have installed updates from Microsoft Update which did, and I had no problem. It may be that Trend has rules to allow certain 'well-known' bootstrappers to execute, or maybe none of them do the same registry access as you do. I'm guessing it's the function UpdateResumeMode in burn\engine\registration.cpp, do you agree? Can you open a bug with this information in it? I'm not exactly sure what we'll do about it but we should at least track the issue. Yes I will do when I'm back in work. I am a bit surprised nobody has seen this; I would have thought that there would be many other corporate users with Trend OfficeScan and a similar config. Pete -- 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
