Re: [WiX-users] Windows Installer 3.1 or 4.5 for XP?
Hi Don, The main feature of WI 4.5 that I found to be the most useful was Transactions, but this is only really an issue if you have a multi package installation. The best option that I am aware of would be to give the customer the chance to take care of the deficiency beforehand. Document it somewhere that the minimum requirement for your program is Windows Installer 4.5, and include a link to the appropriate Microsoft download location. This will allow the user to decide if they want to perhaps schedule the installation for a later time after they have installed WI or if they want to do it immediately. I would still install it as a prerequisite since the user has been potentially forewarned. Mit freundlichen Grüßen / Best regards, Christopher Adkins _ Work Smart - Connect with DocuWare _ DocuWare AG -Original Message- From: Don Walker [mailto:don.wal...@versaterm.com] Sent: Dienstag, 12. Juni 2012 17:56 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Windows Installer 3.1 or 4.5 for XP? I'm likely to be supporting installs on Windows XP until past the MS end of support date. Most of our customers running XP most likely have Windows Installer 3.1 installed. As far as I can tell, upgrading to Windows Installer 4.5 will force a reboot. Should I require Windows 4.5 anyway? I have two concerns about what will happened if I don't upgrade: 1. I'll use some new property or feature that is not supported by Windows Installer 3.1. I discovered after the fact that I had done this when I made use of MsiLogFileLocation and MsiLogging in a custom action before noticing that they weren't supported. The features supported seem to be well-documented at http://msdn.microsoft.com/en-us/library/aa816408%28v=vs.85%29 so as long as I am careful shouldn't be a big issue. 2. I am more concerned that I will end up using some new property or feature that is not supported by Windows Installer 3.1 indirectly through the use of a WiX feature. Some of the WiX features are quite clearly linked to one or more Windows Installer features and can be checked. I'm not really clear if there are a significant number of undocumented dependencies on Windows Installer versions. Upgrading to Windows Installer 4.5 for XP (and Vista) looks like the safest approach. Comments/opinions would be appreciated. -- 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] Wix Toolset installation fails, a bit urgent!
Hi,
I had a few problems with the new Wix Toolset RC, so I decided to reinstall
it, but it keeps failing. I tried to copy paste the links into my browser
and got Network error. Does anyone know when it's gonna get fixed
//Caisa
[06CC:0150][2012-06-13T08:04:36]: Apply begin
[0B00:0780][2012-06-13T08:04:36]: Creating a system restore point.
[0B00:0780][2012-06-13T08:04:36]: Could not create system restore point,
error: 0x80070422. Continuing...
[0B00:0780][2012-06-13T08:04:36]: Caching bundle from:
'C:\DOCUME~1\v0c8665\LOCALS~1\Temp\{ba07efd7-2167-489b-8fb6-336e35564add}\.be\WiX36.exe'
to: 'C:\Documents and Settings\All Users\Application Data\Package
Cache\{ba07efd7-2167-489b-8fb6-336e35564add}\WiX36.exe'
[0B00:0780][2012-06-13T08:04:37]: Registering bundle dependency provider:
{ba07efd7-2167-489b-8fb6-336e35564add}, version: 3.6.2928.0
[06CC:087C][2012-06-13T08:04:37]: Prompt for source of package: Wix,
payload: Wix, path: C:\Downloads\data\core.msi
[06CC:087C][2012-06-13T08:04:37]: Acquiring package: Wix, payload: Wix,
download from: http://wixtoolset.org/releases/3.6.2928.0/data/core.msi
[06CC:087C][2012-06-13T08:05:52]: Error 0x80070003: Failed to send request
to URL: http://wixtoolset.org/releases/3.6.2928.0/data/core.msi
[06CC:087C][2012-06-13T08:05:52]: Error 0x80070003: Failed to connect to
URL: http://wixtoolset.org/releases/3.6.2928.0/data/core.msi
[06CC:087C][2012-06-13T08:05:52]: Error 0x80070003: Failed to get size and
time for URL: http://wixtoolset.org/releases/3.6.2928.0/data/core.msi
[06CC:087C][2012-06-13T08:05:52]: Error 0x80070003: Failed attempt to
download URL: 'http://wixtoolset.org/releases/3.6.2928.0/data/core.msi' to:
'C:\DOCUME~1\v0c8665\LOCALS~1\Temp\{ba07efd7-2167-489b-8fb6-336e35564add}\Wix'
[06CC:087C][2012-06-13T08:05:52]: Error 0x80070003: Failed to acquire
payload from: 'http://wixtoolset.org/releases/3.6.2928.0/data/core.msi' to
working path:
'C:\DOCUME~1\v0c8665\LOCALS~1\Temp\{ba07efd7-2167-489b-8fb6-336e35564add}\Wix'
[06CC:087C][2012-06-13T08:05:52]: Failed to acquire payload: Wix to working
path:
C:\DOCUME~1\v0c8665\LOCALS~1\Temp\{ba07efd7-2167-489b-8fb6-336e35564add}\Wix,
error: 0x80070003.
[06CC:0150][2012-06-13T08:05:52]: Error 0x80070003: Failed while caching,
aborting execution.
[0B00:0780][2012-06-13T08:05:52]: Removed bundle dependency provider:
{ba07efd7-2167-489b-8fb6-336e35564add}
[0B00:0780][2012-06-13T08:05:52]: Removing cached bundle:
{ba07efd7-2167-489b-8fb6-336e35564add}, from path: C:\Documents and
Settings\All Users\Application Data\Package
Cache\{ba07efd7-2167-489b-8fb6-336e35564add}\
[06CC:0150][2012-06-13T08:05:52]: Apply complete, result: 0x80070003,
restart: None, ba requested restart: No
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Toolset-installation-fails-a-bit-urgent-tp7578795.html
Sent from the wix-users mailing list archive at Nabble.com.
--
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] Burn: Exe package can't find payload file that's not a dll.
Hi Matt! You mean like this? This is the way I have it today, and both files are copied to the same package cache folder, but since the installation process of the exe isn't started from that folder it's not going to find the text file. The process is started from the path where the BA.exe is, and that's where it's looking for the text file. When I have the same case but the payload is a dll, then there is no problem (maybe the dll gets registered in GAC?) //Caisa -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Exe-package-can-t-find-payload-file-that-s-not-a-dll-tp7578750p7578794.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Both .Net 3.5 and .Net 4.0 as prereqs?
On 12-Jun-12 11:55, Miss Parker wrote: > If I do that, then .Net 4.0 won't get installed before the BA GUI starts. Or > am I missing something? I tried to put both 3.5 and 4 in the Package group > that's connected to WixMbaPrereqPackageId, but it just crashed. What crashed? What does the log say? -- sig://boB http://joyofsetup.com/ -- 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] Burn: Exe package can't find payload file that's not a dll.
I am not sure exactly how to do this, but you should be able to do what you want by caching the exe payload, and having the text file in the same payload. I know that this is done for MSI files and external cabs, so the engine supports it. But I am not sure of what the syntax would be. I think you will need a payload element under the ExePackage element, but haven't looked up the exact syntax. --matt -Original Message- From: Miss Parker [mailto:caisa.westl...@gmail.com] Sent: Sunday, June 10, 2012 1:50 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Burn: Exe package can't find payload file that's not a dll. Hi, I really need some creative ideas here, some out of the box thinking. I have a situation where an exe package has a payload file (a text file), and for this to work under normal circumstances (without Burn, just double click on the exe) the payload file needs to be placed in the same folder as the exe. But! When I install using Burn and my Bootstrapper application the exe doesn't find the payload file for the simple reason that the installation isn't started in the same folder as where the exe and payload file are placed (package cache\etc...). Since the process is started by the bootstrapper, it also looks for the payload file in that folder. I tried using the layout switch, which worked really well until I realized that when the user downloads the Bootstrapper application he/she might put on the desktop. This means that all the installation files also are put there. Not pretty. My only solution right now is to create an exe that when extracted puts the Bootstrapper app in a new folder somewhere, but I would really like to make this work using Burn instead. Ideas anyone? //Caisa -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Exe-package-can-t-find-payload-file-that-s-not-a-dll-tp7578750.html Sent from the wix-users mailing list archive at Nabble.com. -- 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
Re: [WiX-users] Burn Failure 0x8007051b
Yes - Variable: WixBundleElevated = 1 Could it be that UAC is disabled therefore it is elevated but it actually needs to be an administrator as well? Neil -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: 12 June 2012 20:36 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Burn Failure 0x8007051b On 12-Jun-12 12:15, Neil Sleightholm wrote: > Comparing the logs it looks like burn is not doing the elevate step. Is WixBundleElevated set? -- sig://boB http://joyofsetup.com/ -- 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
Re: [WiX-users] Burn Failure 0x8007051b
On 12-Jun-12 12:15, Neil Sleightholm wrote: > Comparing the logs it looks like burn is not doing the elevate step. Is WixBundleElevated set? -- sig://boB http://joyofsetup.com/ -- 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] Windows Installer 3.1 or 4.5 for XP?
> -Original Message- > From: Don Walker [mailto:don.wal...@versaterm.com] > Sent: Tuesday, June 12, 2012 15:56 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Windows Installer 3.1 or 4.5 for XP? > > I'm likely to be supporting installs on Windows XP until past the MS end of > support date. Most of our customers running XP most likely have Windows > Installer 3.1 installed. As far as I can tell, upgrading to Windows Installer 4.5 > will force a reboot. Should I require Windows 4.5 anyway? What does 4.5 offer that you need, which 3.1 does not? If there are no features in the newer version that you need, then why force your customers to needlessly reboot? Version 3.1 is included with Windows XP SP3, which we require anyway as a prerequisite. As long as they have XP SP3, no reboot is necessary. Since we don't need anything in 4.5, we don't require it. > I have two concerns about what will happened if I don't upgrade: > > 1. I'll use some new property or feature that is not supported by Windows > Installer 3.1. I discovered after the fact that I had done this when I made use > of MsiLogFileLocation and MsiLogging in a custom action before noticing that > they weren't supported. The features supported seem to be well- > documented at http://msdn.microsoft.com/en- > us/library/aa816408%28v=vs.85%29 so as long as I am careful shouldn't be a > big issue. Isn't that what the InstallerVersion attribute of the Package element is for? We use it and haven't had any problems. Of course, as a general rule, I tend to carefully read all documentation about any WiX elements and attributes before using them. That includes both the WiX documentation and the backing Windows Installer documentation on MSDN as well. As you might imagine, I've never accidentally found myself using something that wasn't supported, anyway. (Not carefully reading all documentation equates to sloppy programming that is asking for trouble, in my book.) > > 2. I am more concerned that I will end up using some new property or > feature that is not supported by Windows Installer 3.1 indirectly through the > use of a WiX feature. Some of the WiX features are quite clearly linked to > one or more Windows Installer features and can be checked. I'm not really > clear if there are a significant number of undocumented dependencies on > Windows Installer versions. > > Upgrading to Windows Installer 4.5 for XP (and Vista) looks like the safest > approach. Comments/opinions would be appreciated. -- 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] Should you install 32-bit and 64-bit versions os the same application?
Hi, It's down to the architecture of your software and the needs of your users. Typically you only offer the correct msi per bitness as for most people there is no reason to have both. If you have a lot of plugin developers that will be struggling to keep up and make 64bit versions for your software then you may indeed want to offer then the ability to have both versions installed. This may add complexity that a standard user may find confusing though. The potential dangers lie in the application itself, if you use any shared resources, com objects, registry keys etc. you may have problems installing both side by side as they will clash. The wow64 system can work quite well at isolating some of this for you. But it may also not be what your users expect if they want to switch between bit versions and have their settings etc. be synchronised. You will only know for sure if you do some testing. Dave -Original Message- From: Gareth [mailto:gmor...@serif.com] Sent: 12 June 2012 16:32 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Should you install 32-bit and 64-bit versions os the same application? Thanks for your input Daniel. I all ready have two seperate MSIs for each bitage, and they currently share a ProductGUID to prevent any user installing both, but I'm wondering if this should not be the case and that users should be allowed to install both - as seems necessary fot photo editing apps (or anything with 3rd party plugins, I guess). I can see that a different named shortcut would be required to prevent them clashing, for example. But is there any actual harm in offering both? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Should-you-inst all-32-bit-and-64-bit-versions-os-the-same-application-tp7578776p7578780.html Sent from the wix-users mailing list archive at Nabble.com. - - 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 SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- 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] Burn Failure 0x8007051b
It looks like it has something to do with permissions/uac.
If I create a guest user on a Win7 machine and run the package then I get a
prompt to say I need to provide an admin user and if I do it installs ok. On
the PC with the issue it is a member of the domain and I have logon rights but
not as an admin. When I run the install on this PC I don't get prompted to
provide admin access. If I logon to the PC with a user that does have admin
rights the install runs ok.
Comparing the logs it looks like burn is not doing the elevate step.
Neil
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 12 June 2012 15:01
To: General toolset. (wix-users@lists.sourceforge.net)
Subject: [WiX-users] Burn Failure 0x8007051b
A couple of burn packages built with v3.6.2928.0 are failing on one PC with the
following error:
[0B88:1E3C][2012-06-12T11:19:38]: Plan complete, result: 0x0
[0B88:1E3C][2012-06-12T11:19:38]: Apply begin
[174C:1F10][2012-06-12T11:19:38]: Automatic updates could not be paused due to
error: 0x80070005. Continuing...
[174C:1F10][2012-06-12T11:19:38]: Creating a system restore point.
[174C:1F10][2012-06-12T11:19:38]: Could not create system restore point, error:
0x80070005. Continuing...
[174C:1F10][2012-06-12T11:19:44]: Error 0x8007051b: Failed to secure cache
path: C:\ProgramData\Package Cache\
[174C:1F10][2012-06-12T11:19:44]: Error 0x8007051b: Failed to secure cache
directory: C:\ProgramData\Package Cache\
[174C:1F10][2012-06-12T11:19:44]: Error 0x8007051b: Failed to create completed
cache path for bundle.
[174C:1F10][2012-06-12T11:19:44]: Error 0x8007051b: Failed to cache bundle from
path:
C:\Users\GRANTS~1\AppData\Local\Temp\{d6b43f4b-176b-4555-8d08-c297517fbc19}\.be\Setup.exe
[174C:1F10][2012-06-12T11:19:44]: Error 0x8007051b: Failed to begin
registration session.
[0B88:1E3C][2012-06-12T11:19:44]: Error 0x8007051b: Failed to begin
registration session in per-machine process.
[0B88:1E3C][2012-06-12T11:19:44]: Error 0x8007051b: Failed to register bundle.
[0B88:1E3C][2012-06-12T11:19:45]: Apply complete, result: 0x8007051b, restart:
None, ba requested restart: No
[0B88:1E3C][2012-06-12T11:21:30]: Shutting down, exit code: 0x8007051b
0x8007051b = This security ID may not be assigned as the owner of this object.
Any idea what is causing this?
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com
--
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] Windows Installer 3.1 or 4.5 for XP?
I'm likely to be supporting installs on Windows XP until past the MS end of support date. Most of our customers running XP most likely have Windows Installer 3.1 installed. As far as I can tell, upgrading to Windows Installer 4.5 will force a reboot. Should I require Windows 4.5 anyway? I have two concerns about what will happened if I don't upgrade: 1. I'll use some new property or feature that is not supported by Windows Installer 3.1. I discovered after the fact that I had done this when I made use of MsiLogFileLocation and MsiLogging in a custom action before noticing that they weren't supported. The features supported seem to be well-documented at http://msdn.microsoft.com/en-us/library/aa816408%28v=vs.85%29 so as long as I am careful shouldn't be a big issue. 2. I am more concerned that I will end up using some new property or feature that is not supported by Windows Installer 3.1 indirectly through the use of a WiX feature. Some of the WiX features are quite clearly linked to one or more Windows Installer features and can be checked. I'm not really clear if there are a significant number of undocumented dependencies on Windows Installer versions. Upgrading to Windows Installer 4.5 for XP (and Vista) looks like the safest approach. Comments/opinions would be appreciated. -- 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] Both .Net 3.5 and .Net 4.0 as prereqs?
If I do that, then .Net 4.0 won't get installed before the BA GUI starts. Or am I missing something? I tried to put both 3.5 and 4 in the Package group that's connected to WixMbaPrereqPackageId, but it just crashed. But thanks anyway! //Caisa -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Both-Net-3-5-and-Net-4-0-as-prereqs-tp7578749p7578784.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Burn: Exe package can't find payload file that's not a dll.
That would work if I had any sort of control over the exe, but I don't. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Exe-package-can-t-find-payload-file-that-s-not-a-dll-tp7578750p7578783.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Light.exe error: Value cannot be null
Hi, I upgraded to Wix Toolset RC today, and suddenly some MsiPackage elements in my bundle generated an error: "Value cannot be null" (Light.exe) There are absolutely nothing special about the packages, and there were no problems building the BA before the upgrade. Does anyone know what causes this particular error? //Caisa -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Light-exe-error-Value-cannot-be-null-tp7578782.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Burn Failure 0x8007051b
I don't have an answer for you, but I got a similar error (the registration errors) during uninstall and that caused the uninstall to fail. It would be nice to know what's causing this. //Caisa -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Failure-0x8007051b-tp7578778p7578781.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Should you install 32-bit and 64-bit versions os the same application?
Thanks for your input Daniel. I all ready have two seperate MSIs for each bitage, and they currently share a ProductGUID to prevent any user installing both, but I'm wondering if this should not be the case and that users should be allowed to install both - as seems necessary fot photo editing apps (or anything with 3rd party plugins, I guess). I can see that a different named shortcut would be required to prevent them clashing, for example. But is there any actual harm in offering both? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Should-you-install-32-bit-and-64-bit-versions-os-the-same-application-tp7578776p7578780.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Deleting user.config after uninstall?
There's this, not official but useful... http://blogs.msdn.com/b/oldnewthing/archive/2007/09/17/4948130.aspx Phil W From: Jerra [beddel...@gmail.com] Sent: Tuesday, June 12, 2012 12:22 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Deleting user.config after uninstall? OK thanks! Well installation is sort of a gigantic big black hole I am trying to understand. Luckily there is a lot of info on the web regarding WiX and this mailing list. MS guidelines, I haven't seen any of those though.. > System preferences... Now that's a different beast :) I do not understand this remark. /Jerra On 12.6.2012 10:14, Sascha Beaumont wrote: > Refer the ms guidelines, user data should remain after uninstall. So leaving > a trail that is expected. > > System preferences... Now that's a different beast :) > > Cheers, > Sascha > > On 11/06/2012, at 11:52 PM, Jerra wrote: > >> In my application I use the built in functionality for storing user settings >> (Settings.Default.xyz) which generates a user.config file. >> >> I am leaving a trail of these old user.config files. How on earth do I >> remove these using WiX. I can't hardcode () the location as it >> is unknown at installation where they will be stored. Attaching a screendump >> of my garbage. >> >> I guess some kind of recursive search in [user]\AppData\Local and deleting >> all my application files would be quite reckless. >> >> Any help greatly appreciated, >> Jerra >> >> -- >> Visual Studio 2010 Professional >> WiX 3.5 >> Programming in C# /.NET 4.0 >> -- >> 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 > -- Visual Studio 2010 Professional WiX 3.5 Programming in C# /.NET 4.0 -- 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 *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- 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/ ___ Wi
[WiX-users] Burn Failure 0x8007051b
A couple of burn packages built with v3.6.2928.0 are failing on one PC with the
following error:
[0B88:1E3C][2012-06-12T11:19:38]: Plan complete, result: 0x0
[0B88:1E3C][2012-06-12T11:19:38]: Apply begin
[174C:1F10][2012-06-12T11:19:38]: Automatic updates could not be paused due to
error: 0x80070005. Continuing...
[174C:1F10][2012-06-12T11:19:38]: Creating a system restore point.
[174C:1F10][2012-06-12T11:19:38]: Could not create system restore point, error:
0x80070005. Continuing...
[174C:1F10][2012-06-12T11:19:44]: Error 0x8007051b: Failed to secure cache
path: C:\ProgramData\Package Cache\
[174C:1F10][2012-06-12T11:19:44]: Error 0x8007051b: Failed to secure cache
directory: C:\ProgramData\Package Cache\
[174C:1F10][2012-06-12T11:19:44]: Error 0x8007051b: Failed to create completed
cache path for bundle.
[174C:1F10][2012-06-12T11:19:44]: Error 0x8007051b: Failed to cache bundle from
path:
C:\Users\GRANTS~1\AppData\Local\Temp\{d6b43f4b-176b-4555-8d08-c297517fbc19}\.be\Setup.exe
[174C:1F10][2012-06-12T11:19:44]: Error 0x8007051b: Failed to begin
registration session.
[0B88:1E3C][2012-06-12T11:19:44]: Error 0x8007051b: Failed to begin
registration session in per-machine process.
[0B88:1E3C][2012-06-12T11:19:44]: Error 0x8007051b: Failed to register bundle.
[0B88:1E3C][2012-06-12T11:19:45]: Apply complete, result: 0x8007051b, restart:
None, ba requested restart: No
[0B88:1E3C][2012-06-12T11:21:30]: Shutting down, exit code: 0x8007051b
0x8007051b = This security ID may not be assigned as the owner of this object.
Any idea what is causing this?
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com
--
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] Should you install 32-bit and 64-bit versions os the same application?
Hello Gareth, I am not an expert on installation but I use WiX to install both 32-bit and 64-bit components on a 64-bit machine using a single installer and it has been working fine for me. In fact, since our "application" is essentially a plugin for a third-party application that comes in both 32-bit and 64-bit varieties, we install the 32-bit or 64-bit components based on whether the 32-bit or 64-bit version of the third-party application is installed. What I really like about WiX is that I can build a 32-bit installer for a 32-bit O/S as well as a 64-bit installer that includes both 32-bit and 64-bit components for a 64-bit O/S from the same source files by using the WiX preprocessor facilities. Sincerely, Daniel Madill -Original Message- From: Gareth [mailto:gmor...@serif.com] Sent: June-12-12 6:40 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Should you install 32-bit and 64-bit versions os the same application? When I first looked into creating a 64-bit package to sit alongside our existing 32-bit package it seemed obvious to me that you should offer one or the other, which ever is appropriate for the user's OS. And most of what I've read supports this. However, Adobe PhotoShop offer the option to install both on 64-bit OS. I can understand that you might need both because of the compatability of your plugins so you can perform most of your work in 64-bit, but occasionally use the 32-bit version where plugin compatability is required. But should this approach be the norm - should you offer the option to install both 32-bit and 64-bit on 64-bit OS as a matter of habit? Does this approach cause any issues that should be viewed with caution? Cheers, G -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Should-you-install-32-bit-and-64-bit-versions-os-the-same-application-tp7578776.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Should you install 32-bit and 64-bit versions os the same application?
When I first looked into creating a 64-bit package to sit alongside our existing 32-bit package it seemed obvious to me that you should offer one or the other, which ever is appropriate for the user's OS. And most of what I've read supports this. However, Adobe PhotoShop offer the option to install both on 64-bit OS. I can understand that you might need both because of the compatability of your plugins so you can perform most of your work in 64-bit, but occasionally use the 32-bit version where plugin compatability is required. But should this approach be the norm - should you offer the option to install both 32-bit and 64-bit on 64-bit OS as a matter of habit? Does this approach cause any issues that should be viewed with caution? Cheers, G -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Should-you-install-32-bit-and-64-bit-versions-os-the-same-application-tp7578776.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Deploying WiX bootstrappers (SCCM, GPO, etc.)
I'm a developer, not an IT guy too, so it's not anything I've ever done, just read about :) Yes, login scripts are similar to start-up scripts but run during login, rather than computer start up. I guess youd use a startup script for a per-machine MSI and a login script for a per-user MSI. You assign login scripts via group policy. It's not an ideal way to deploy but it'll work. This link should help better than I http://technet.microsoft.com/en-us/magazine/dd630947.aspx -Original Message- From: Don Walker [mailto:don.wal...@versaterm.com] Sent: 11 June 2012 22:30 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Deploying WiX bootstrappers (SCCM, GPO, etc.) Peter, thanks for your reply. I'm a developer, not an IT guy, so please excuse me if the following questions are too basic. I wasn't aware that you could install software remotely using login scripts. Are these the same as startup scripts? See http://www.mombu.com/microsoft/windows-group-policy/t-deploy-a-bat-file-using -gpo-137163.html - look for "Active Directory Computer Startup Script". Would an IT department with the ability to deploy using GPO's also have the ability to run login/startup scripts? If so, it would appear to be a fairly simple matter to deploy exe-based installers. Do you prefer one scripting language over another? I would want to use a simple cmd file if possible. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-WiX-b ootstrappers-SCCM-GPO-etc-tp7578746p7578764.html Sent from the wix-users mailing list archive at Nabble.com. - - 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 SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- 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] heat parameters for harvesting a reg file
I want to harvest a reg file using heat. The wxs file is generated using: heat reg data.reg" -ag -sfrag -cg Registry -o Registry.wxs The call to heat succeeds but when I build the installer the following error message occurs: Registry.wxs (4): The Directory element requires the Name attribute because there is no parent Directory element. Registry.wxs (4): The 'TARGETDIR' directory has an illegal DefaultDir value of '.'. The DefaultDir value is created from the *Name attributes of the Directory element. The TARGETDIR directory is a special directory which must have its Name attribute set to 'SourceDir'. The wxs looks like this: http://schemas.microsoft.com/wix/2006/wi";> ... What are the right parameters for heat for processing reg files? How do i include the generated wxs to my main wxs file? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-parameters-for-harvesting-a-reg-file-tp7578774.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Deleting user.config after uninstall?
OK thanks! Well installation is sort of a gigantic big black hole I am trying to understand. Luckily there is a lot of info on the web regarding WiX and this mailing list. MS guidelines, I haven't seen any of those though.. > System preferences... Now that's a different beast :) I do not understand this remark. /Jerra On 12.6.2012 10:14, Sascha Beaumont wrote: > Refer the ms guidelines, user data should remain after uninstall. So leaving > a trail that is expected. > > System preferences... Now that's a different beast :) > > Cheers, > Sascha > > On 11/06/2012, at 11:52 PM, Jerra wrote: > >> In my application I use the built in functionality for storing user settings >> (Settings.Default.xyz) which generates a user.config file. >> >> I am leaving a trail of these old user.config files. How on earth do I >> remove these using WiX. I can't hardcode () the location as it >> is unknown at installation where they will be stored. Attaching a screendump >> of my garbage. >> >> I guess some kind of recursive search in [user]\AppData\Local and deleting >> all my application files would be quite reckless. >> >> Any help greatly appreciated, >> Jerra >> >> -- >> Visual Studio 2010 Professional >> WiX 3.5 >> Programming in C# /.NET 4.0 >> -- >> 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 > -- Visual Studio 2010 Professional WiX 3.5 Programming in C# /.NET 4.0 -- 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] Deleting user.config after uninstall?
Refer the ms guidelines, user data should remain after uninstall. So leaving a trail that is expected. System preferences... Now that's a different beast :) Cheers, Sascha On 11/06/2012, at 11:52 PM, Jerra wrote: > In my application I use the built in functionality for storing user settings > (Settings.Default.xyz) which generates a user.config file. > > I am leaving a trail of these old user.config files. How on earth do I remove > these using WiX. I can't hardcode () the location as it is > unknown at installation where they will be stored. Attaching a screendump of > my garbage. > > I guess some kind of recursive search in [user]\AppData\Local and deleting > all my application files would be quite reckless. > > Any help greatly appreciated, > Jerra > > -- > Visual Studio 2010 Professional > WiX 3.5 > Programming in C# /.NET 4.0 > -- > 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
