Re: [WiX-users] creating a WIX small or minor patch
Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a bit more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. !-- Id must be higher than any sequence number in the baseline msi's Media/File table. Cabinet must match the original cabinet file name. -- Media Id=5728 Cabinet=Product.cab !-- Id created for the patches' baseline. Referenced in the command line. -- PatchBaseline Id=SP3 / /Media -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, RD QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. - - 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 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
Re: [WiX-users] creating a WIX small or minor patch
The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a bit more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. !-- Id must be higher than any sequence number in the baseline msi's Media/File table. Cabinet must match the original cabinet file name. -- Media Id=5728 Cabinet=Product.cab !-- Id created for the patches' baseline. Referenced in the command line. -- PatchBaseline Id=SP3 / /Media -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, RD QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. - - 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 SDL PLC confidential, all rights reserved. If you are
Re: [WiX-users] Icon for util:InternetShortcut
I've got it semi working:
DirectoryRef Id=MyStartMenuFolder
Component Id=UrlShortcut Guid=* KeyPath=yes
IniFile Id=UrlShortcutURL Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=URL Value=http://localhost:8080/mysite; /
IniFile Id=UrlShortcutHotKey Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=HotKey Value=0 /
IniFile Id=UrlShortcutIconFile Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=IconFile Value=[#MyIcon.ico] /
IniFile Id=UrlShortcutIconIndex Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=IconIndex Value=0 /
IniFile Id=UrlShortcutProp3 Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section={000214A0---C000-0046} Key=Prop3 Value=19,2 /
/Component
/DirectoryRef
DirectoryRef Id=INSTALLDIR
Component Id=MyIcon.ico Guid=*
File Id=MyIcon.ico KeyPath=yes Source=Resources\MyIcon.ico /
/Component
/DirectoryRef
Yet the icon does not show up - however, if I copy this URL shortcut or
move it to the desktop, the icon shows. Maybe a bug in Windows, or maybe
something to do with the last Prop3 value as I don't know what that's for!
Regards,
Dan
On Tue, Jan 17, 2012 at 2:48 PM, Dan Gough goug...@gmail.com wrote:
You can try writing your URL file from the IniFile table instead, as .URL
files are in INI format. I am going to try exactly this later on today,
I've done it before (but not in WiX) so it should work. I'll post my
sample code if you need me to.
Regards,
Dan
On Sun, Jan 15, 2012 at 4:32 AM, Bob Arnson b...@joyofsetup.com wrote:
On 13-Jan-12 04:12, Michael Scheepers wrote:
I like to define an icon for this menu item but I can't find any
property to set anIcon reference for example. Is there a way to
define an image which is used for the internet short cut?
Not currently supported. There's an open feature request but so far
nobody's volunteered to implement it.
--
sig://boB
http://joyofsetup.com/
--
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] Icon for util:InternetShortcut
Seems to be working now after adding empty IniFile entry for IDList, using
[~] to specify a null value (as the schema does not allow null values):
IniFile Id=UrlShortcutIDList Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=IDList Value=[~] /
On Wed, Jan 18, 2012 at 1:06 PM, Dan Gough goug...@gmail.com wrote:
I've got it semi working:
DirectoryRef Id=MyStartMenuFolder
Component Id=UrlShortcut Guid=* KeyPath=yes
IniFile Id=UrlShortcutURL Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=URL Value=http://localhost:8080/mysite;
/
IniFile Id=UrlShortcutHotKey Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=HotKey Value=0 /
IniFile Id=UrlShortcutIconFile Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=IconFile Value=[#MyIcon.ico] /
IniFile Id=UrlShortcutIconIndex Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=IconIndex Value=0 /
IniFile Id=UrlShortcutProp3 Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section={000214A0---C000-0046} Key=Prop3 Value=19,2 /
/Component
/DirectoryRef
DirectoryRef Id=INSTALLDIR
Component Id=MyIcon.ico Guid=*
File Id=MyIcon.ico KeyPath=yes Source=Resources\MyIcon.ico
/
/Component
/DirectoryRef
Yet the icon does not show up - however, if I copy this URL shortcut or
move it to the desktop, the icon shows. Maybe a bug in Windows, or maybe
something to do with the last Prop3 value as I don't know what that's for!
Regards,
Dan
On Tue, Jan 17, 2012 at 2:48 PM, Dan Gough goug...@gmail.com wrote:
You can try writing your URL file from the IniFile table instead, as .URL
files are in INI format. I am going to try exactly this later on today,
I've done it before (but not in WiX) so it should work. I'll post my
sample code if you need me to.
Regards,
Dan
On Sun, Jan 15, 2012 at 4:32 AM, Bob Arnson b...@joyofsetup.com wrote:
On 13-Jan-12 04:12, Michael Scheepers wrote:
I like to define an icon for this menu item but I can't find any
property to set anIcon reference for example. Is there a way to
define an image which is used for the internet short cut?
Not currently supported. There's an open feature request but so far
nobody's volunteered to implement it.
--
sig://boB
http://joyofsetup.com/
--
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] Icon for util:InternetShortcut
Hi Dan,
thanks for figuring out. I tested it without the mysterious Prop3
key and, however, it works fine...
Thanks again
Michel
Am 18.01.2012 14:34, schrieb Dan Gough:
Seems to be working now after adding empty IniFile entry for IDList, using
[~] to specify a null value (as the schema does not allow null values):
IniFile Id=UrlShortcutIDList Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=IDList Value=[~] /
On Wed, Jan 18, 2012 at 1:06 PM, Dan Goughgoug...@gmail.com wrote:
I've got it semi working:
DirectoryRef Id=MyStartMenuFolder
Component Id=UrlShortcut Guid=* KeyPath=yes
IniFile Id=UrlShortcutURL Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=URL Value=http://localhost:8080/mysite;
/
IniFile Id=UrlShortcutHotKey Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=HotKey Value=0 /
IniFile Id=UrlShortcutIconFile Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=IconFile Value=[#MyIcon.ico] /
IniFile Id=UrlShortcutIconIndex Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section=InternetShortcut Key=IconIndex Value=0 /
IniFile Id=UrlShortcutProp3 Action=addLine
Directory=MyStartMenuFolder Name=Shortcut.url
Section={000214A0---C000-0046} Key=Prop3 Value=19,2 /
/Component
/DirectoryRef
DirectoryRef Id=INSTALLDIR
Component Id=MyIcon.ico Guid=*
File Id=MyIcon.ico KeyPath=yes Source=Resources\MyIcon.ico
/
/Component
/DirectoryRef
Yet the icon does not show up - however, if I copy this URL shortcut or
move it to the desktop, the icon shows. Maybe a bug in Windows, or maybe
something to do with the last Prop3 value as I don't know what that's for!
Regards,
Dan
On Tue, Jan 17, 2012 at 2:48 PM, Dan Goughgoug...@gmail.com wrote:
You can try writing your URL file from the IniFile table instead, as .URL
files are in INI format. I am going to try exactly this later on today,
I've done it before (but not in WiX) so it should work. I'll post my
sample code if you need me to.
Regards,
Dan
On Sun, Jan 15, 2012 at 4:32 AM, Bob Arnsonb...@joyofsetup.com wrote:
On 13-Jan-12 04:12, Michael Scheepers wrote:
I like to define an icon for this menu item but I can't find any
property to set anIcon reference for example. Is there a way to
define an image which is used for the internet short cut?
Not currently supported. There's an open feature request but so far
nobody's volunteered to implement it.
--
sig://boB
http://joyofsetup.com/
--
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
--
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] Adding Internet Explorer Context Menu item for all users in a per machine install
For reasons that boggle my mind I changed my RegistryValue Elements to include the Name attribute where before they only had the path and a key value, where the value included the new key to be created. I also removed the initial item that added a Default value of the Product Name which was outlined in the original help / example for using Active Setup. So for those playing along at home all you need are: 3 values to get this to work for a per machine install: Root=HKLM Key=Software\Microsoft\Active Setup\Installed Components\[ProductCode] Name=StubPath Root=HKLM Key=Software\Microsoft\Active Setup\Installed Components\[ProductCode] Name=Version Root=HKCU Key=Software\Microsoft\Active Setup\Installed Components\[ProductCode] Name=Version The latter is so that the installing user doesn't have the repair install done on their machine the next time they logoff and logon. One thing to note that I was unsure of was will the user see the repair install. There was discussion on the forums that /qn should be used instead of /qb. I can tell you that for a brand new user logging in /qb doesn't result in the user seeing anything. I rebuilt the install with /qn and ran the test again to see what would happen. Jon From: McCain, Jon Sent: Tuesday, January 17, 2012 4:37 PM To: chr...@iswix.com; General discussion for Windows Installer XML toolset.; Wilson, Phil; Dan Gough Cc: McCain, Jon Subject: RE: [WiX-users] Adding Internet Explorer Context Menu item for all users in a per machine install Thanks for the quick response Chris. My issue is that the keys are NEVER copied into HKCU on XP or Win 7 64bit. I would love to see a working example though if you don't mind. Thanks again. Jon From: Christopher Painter [mailto:chr...@iswix.com]mailto:[mailto:chr...@iswix.com] Sent: Tuesday, January 17, 2012 4:16 PM To: McCain, Jon; General discussion for Windows Installer XML toolset.; Wilson, Phil; Dan Gough Cc: McCain, Jon Subject: RE: [WiX-users] Adding Internet Explorer Context Menu item for all users in a per machine install ActiveSetup predates MSI and doens't really know anything about MSI. The only thing that ActiveSetup copies is the version registry value so that it knows it doesn't need to run again. What active setup really does is run a program. This program could be Notepad but in our case it's msiexec to get MSI to repair itself and install the HKCU registry components. Make sense? I can send you some sample WXS tonight if you still need it. From: McCain, Jon jon.mcc...@inin.commailto:jon.mcc...@inin.com Sent: Tuesday, January 17, 2012 3:08 PM To: chr...@iswix.commailto:chr...@iswix.com chr...@iswix.commailto:chr...@iswix.com, General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net, Wilson, Phil phil.wil...@invensys.commailto:phil.wil...@invensys.com, Dan Gough goug...@gmail.commailto:goug...@gmail.com Subject: RE: [WiX-users] Adding Internet Explorer Context Menu item for all users in a per machine install Okay last question here... Does Active Setup require that some component be set as ADVERTISED? I have not been able to see Active Setup copy ANYTHING from HKLM to HKCU for the non-installing user. There has got to be a way to get this to work that I am just blindly not seeing. Jon -Original Message- From: McCain, Jon Sent: Sunday, January 15, 2012 10:44 AM To: chr...@iswix.commailto:chr...@iswix.com; General discussion for Windows Installer XML toolset.; Wilson, Phil; Dan Gough Cc: McCain, Jon Subject: RE: [WiX-users] Adding Internet Explorer Context Menu item for all users in a per machine install I'll try it again with a fresh image but my understanding based on the links is that the replication should occur if the key is not there or if the version is higher in the HKLM Active Setup key. When each user logs in that replication should occur and then launch that repair. From what I have seen so far the replication is not occurring at all therefore not getting to the repair portion. As I said though I'll try it again on a clean machine just to be %100 sure. Although Phil stated that it had to be with an advertised shortcut which in my case I am NOT doing... Chris are you saying that is necessary as well? Thanks, Jon -Original Message- From: Christopher Painter [mailto:chr...@iswix.com]mailto:[mailto:chr...@iswix.com] Sent: Friday, January 13, 2012 3:40 PM To: Wilson, Phil; General discussion for Windows Installer XML toolset.; Dan Gough Subject: Re: [WiX-users] Adding Internet Explorer Context Menu item for all users in a per machine install Actually I just realized I've been saying it all. I've been implying that the repair approach and the active setup approach are mutually exclusive. In fact the active setup is just a way to trigger the repair through a command line when an advertised shortcut is unavailable. I'm sorry
Re: [WiX-users] difx extension and perMachine installs
You may have signed with your self-signed certificate, and you may even have added it to some random place in the certificate store, but your driver isn't WHQL signed. Please review these topics, depending on what your operating system is: http://msdn.microsoft.com/en-us/library/ff543654(VS.85).aspx Specifically, they state the following regarding quiet installation (which you are trying to do by turning off Legacy): * Windows Vista/7 quiet install of Authenticode-signed non-WHQL driver: If the certificate that was used to sign the driver package is not installed in the user's certificate stores [Trusted Publishers I believe] before the installation, the installation will fail. To be precise, even if you sign your driver with Authenticode with VeriSign / trusted root CA, you can't install it quietly on a fresh copy of Windows because it's not WHQL-class and your certificate isn't in Trusted Publishers. Only WHQL-class, Authenticode-signed drivers can be installed quietly on a clean copy of Windows. * Windows XP quiet install of Authenticode-signed non-WHQL driver: Because of a limitation in Windows XP and Windows 2000, the DIFx tools cannot perform a quiet installation of PnP function drivers. Have you even tried turning on the Legacy option? I bet you'll still get some warnings that you have to click through when you turn Legacy on. Just try it and see what happens! The thing to do is probably just turn Legacy on for development. Once you have your driver WHQL signed, turn it off. Maybe you can get around this on Windows Vista by adding your self-signed cert to both trusted root CAs and trusted publishers, I don't know. Never bothered to try. The only real solution that works is something WHQL-signed, and I believe the Authenticode signature has to come from VeriSign. Then you can turn Legacy off and it will work on Windows 2000 and up. Your original e-mail that stated you got the TRUST_E_NOSIGNATURE error makes it pretty obvious what the problem is - you don't have a valid signature for some reason. Turn on Legacy mode, and the resulting prompts may give you some clues as to what is going on. Regarding per-user vs. per-machine: I don't really see how it's possible to do per-user when a driver is installed. I set my install (which includes drivers) to be per-machine only to avoid confusion. James -Original Message- From: Peter Hull [mailto:peterhul...@hotmail.com] Sent: Tuesday, January 17, 2012 22:17 To: WiX Users Subject: 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 -- 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] How to bring a VBScript window in front of the wizard window?
On 1/17/12 7:49 PM, Christopher Painter wrote: I find it more elegant to have the custom action only set a property and return. Then on the remaining control events use the property in a condition to perform a SpawnDialog on a custom dialog that displayes the error message. This way MSI continues to handle the UI. Thank you for your suggestion, Christopher. I wish I wouldn't need to deal with GUI. This particular code is for testing/debugging, and so having this come out under the wizard window is OK. But I would eventually need to have a dialog to let user choose a file. Because the stock custome controls don't include a file dialog, I think I need to use scripting. Would there be any other way around that hopefully doesn't involve writing a DLL? I have another (hopefully the last) related question. After searching the Internet, I came up with this VBScript CustomAction Id=AskLicense Script=vbscript ![CDATA[ Dim ObjFSO Set ObjFSO = CreateObject(UserAccounts.CommonDialog) ObjFSO.Filter = License File|*.xml ObjFSO.FilterIndex = 3 ObjFSO.InitialDir = C:\ Session.Property(SELECTEDRLPLICENSEFILE) = ObjFSO.FileName ]] /CustomAction This didn't work. I got an error pop up, and the MSI log has this entry: MSI (s) (4C:C8) [18:29:53:667]: Hello, I'm your 32bit Impersonated custom action server. Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action AskLicense script error -2146827859, Microsoft VBScript runtime error: ActiveX component can't create object: 'UserAccounts.CommonDialog' Line 2, Column 1, Apparently, CreateObject(UserAccounts.CommonDialog) couldn't create the window. Do I use some other mean to create a dialog under MSI? Kuro From: T. Kuro Kurosakak...@basistech.com Sent: Tuesday, January 17, 2012 7:20 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to bring a VBScript window in front of the wizard window? I have this wix code that calls a VBScript code to show a window: CustomAction Id=AskLicense Script=vbscript ![CDATA[ MsgBox The License File Path will be asked here by a file dialog eventually., 1, License File Needed Session.Property(SELECTEDRLPLICENSEFILE) = C:/dummy/location/foo.txt ]] /CustomAction InstallExecuteSequence Custom Action=AskLicense After=InstallValidateNot Installed/Custom /InstallExecuteSequence The window is shown but it's hidden under the wizard window. How can I bring it to the front, or else side of the wizard window? Kuro -- 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
[WiX-users] Next Release of Version 3.6
Is there a time line for the next release of 3.6? (RC or any update to the original Oct Release). Thanks, Bruce Bruce Gombrelli Sr. Software Engineer Experis v-bru...@microsoft.com cell: 425-614-7517 -- 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] Uninstall fails for burn bootstrapper
Bug in Burn around caching and not being able to find files in attached
container. Should be fixed soon.
On Wed, Jan 18, 2012 at 5:34 AM, Michael Scheepers mscheep...@tool-links.de
wrote:
Hi there,
I just started using burn as bootstrapper application to install a
specific java jdk if it is not present before an application will be
installed. Here is the code I use (it only contains the jdk):
file *jdk-6u27-x64.wxs*:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Fragment
util:RegistrySearch Id=rs_jdk Variable=jdk_version Win64=yes
Root=HKLM
Key=SOFTWARE\JavaSoft\Java Development Kit
Value=CurrentVersion /
PackageGroup Id=PGJavaJDK
ExePackage Id=JavaJDK
SourceFile=D:\transfer\jdk-6u27-windows-x64.exe
InstallCommand=/qr /ACTION=Install
RepairCommand=/qr ACTION=Repair /hideconsole
UninstallCommand=/qr ACTION=Uninstall /hideconsole
DetectCondition=jdk_version gt;= quot;1.6quot;
InstallCondition=VersionNT64
Vital=yes PerMachine=yes /
/PackageGroup
/Fragment
/Wix
--
file *bundle.wxs*:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Bundle Name=Bootstrapper1 Version=1.0.0.0 Manufacturer=SAPERION
AG UpgradeCode=5efcf222-6acb-4243-8dd5-e55b509543b7
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense /
Chain
PackageGroupRef Id=PGJavaJDK/
/Chain
/Bundle
/Wix
--
After starting the setup it worked as expected. Because I had the jdk
already installed it did nothing, but it appeared in the Control Panel
- Programs and Features list. Ok so far, but if I try to uninstall
that bootstrapper it fails and the log contains:
[1674:27D8][2012-01-18T14:14:55]: Burn v3.6.2221.0, path:
C:\ProgramData\Package
Cache\{b0549451-e6c8-4c45-a7d0-bc87d11a79c4}\Bootstrapper1.exe, cmdline:
'/uninstall -burn.unelevated
BurnPipe.{E1D0F248-C7E8-453A-86CE-12A48A58A72D}
{E2142AF5-67B8-41B5-9E67-D01018BA3EFF} 9300'
[1674:27D8][2012-01-18T14:14:55]: Setting string variable
'WixBundleName' to value 'Bootstrapper1'
[1674:27D8][2012-01-18T14:14:55]: Setting string variable 'WixBundleLog'
to value 'C:\Users\mls\AppData\Local\Temp\Bootstrapper1_20120118141455.log'
[1674:27D8][2012-01-18T14:14:56]: Detect 1 packages
[1674:27D8][2012-01-18T14:14:56]: Setting string variable 'jdk_version'
to value '1.6'
[1674:27D8][2012-01-18T14:14:56]: Detected related bundle:
{b7d415d7-34f7-4657-a3eb-79d00d1fc6e4}, scope: PerMachine, version:
1.0.0.0, operation: None
[1674:27D8][2012-01-18T14:14:56]: Condition 'jdk_version = 1.6'
evaluates to true.
[1674:27D8][2012-01-18T14:14:56]: Detected package:
jdk_6u27_windows_x64.exe, state: Present, cached: No
[1674:27D8][2012-01-18T14:14:56]: Detect complete, result: 0x0
[1674:27D8][2012-01-18T14:14:58]: Plan 1 packages, action: Uninstall
[1674:27D8][2012-01-18T14:14:58]: Setting string variable
'WixBundleLog_jdk_6u27_windows_x64.exe' to value
'C:\Users\mls\AppData\Local\Temp\Bootstrapper1_20120118141455_0_jdk_6u27_windows_x64.exe.log'
[1674:27D8][2012-01-18T14:14:58]: Setting string variable
'WixBundleRollbackLog_jdk_6u27_windows_x64.exe' to value
'C:\Users\mls\AppData\Local\Temp\Bootstrapper1_20120118141455_0_jdk_6u27_windows_x64.exe_rollback.log'
[1674:27D8][2012-01-18T14:14:58]: Planned package:
jdk_6u27_windows_x64.exe, state: Present, default requested: Absent, ux
requested: Absent, execute: Uninstall, rollback: Install, cache: Yes,
uncache: Yes, dependency: Unregister
[1674:27D8][2012-01-18T14:14:58]: Plan complete, result: 0x0
[1674:27D8][2012-01-18T14:14:58]: Apply begin
[1674:2500][2012-01-18T14:14:58]: Error 0x80004005: Failed to extract
all files from container.
[1674:1EBC][2012-01-18T14:14:58]: Error 0x80004005: Failed to wait for
operation complete.
[1674:1EBC][2012-01-18T14:14:58]: Error 0x80004005: Failed to open
container.
[1674:1EBC][2012-01-18T14:14:58]: Error 0x80004005: Failed to open
container: WixAttachedContainer.
[1674:1EBC][2012-01-18T14:14:58]: Failed to extract payloads from
container: WixAttachedContainer to working path: (null), error: 0x80004005.
[1674:1EBC][2012-01-18T14:14:58]: Error 0x80004005: Failed to cache
packages.
[1674:27D8][2012-01-18T14:14:58]: Error 0x80004005: Failed while waiting
for cache thread to complete before executing.
[1674:27D8][2012-01-18T14:14:58]: Apply complete, result: 0x80004005
restart: No
What I see in the log, if I construe it right is, that the bootstrapper
tried to uninstall a package that he didn't install, because it was
already present. I guess that is not the wanted behavior, or did I miss
something?
Well the least problem is, that I can't get rid of the entry in programs
and features...
Regards
Michel
[WiX-users] Wix Weekly Builds?
Are weekly builds available again yet? I was going to upgrade our installers to use a more recent build, but could not find them. Rob's blog mentioned that they were on track, but it still points to October's build. John -- 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
[WiX-users] WiX Burn: Error 0x800b0100: Failed authenticode verification of payload
Hi there,
We recently deployed one of our burn bootstrappers and have received a
bunch of errors during the testing so we had to take it down for the
moment.
One of the problems that we were getting was that burn failed authenticode
verification of payload. What does that mean? The payloads that we are
downloading are MSI files that are digitally signed by a third party (e.g
SQL Server signed by Microsoft, Crystal Reports signed by Business
Objects). We haven't modified the signatures since we built the bundle. How
can we fix this error?
Here is the log of the error:
[0D48:0F18][2012-01-18T12:18:
10]: Error 0x800b0100: Failed authenticode verification of payload:
C:\DOCUME~1\tareshs\LOCALS~1\Temp\{d9229fea-2a5b-4065-ad91-26acb1c19a29}\SQLEXPR_x86.exe
[0D48:0F18][2012-01-18T12:18:10]: Error 0x800b0100: Failed to verify
payload signature: C:\Documents and Settings\All Users\Application
Data\Package Cache\AAD3148BBD879B13A261C6A2A0C4BEFAFD3A6871\SQLEXPR_x86.exe
[0D48:0F18][2012-01-18T12:18:10]: Error 0x800b0100: Failed to cache payload.
[06A8:0EA8][2012-01-18T12:18:10]: Failed to cache payload: SQLEXPR_x86.exe
from working path:
C:\DOCUME~1\tareshs\LOCALS~1\Temp\{d9229fea-2a5b-4065-ad91-26acb1c19a29}\SQLEXPR_x86.exe,
error: 0x800b0100.
Thanks,
--
Sunny Li
--
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] How to bring a VBScript window in front of the wizard window?
BTW, I found an answer to my original question. I needed to pass 4096 instead of 1 in the second argument like this: MsgBox The License File Path will be asked here by a file dialog eventually., 4096, License File Needed Here 4096 = vbOKOnly(0) + vbSystemModal(4096) where these constants are listed in: http://msdn.microsoft.com/en-us/library/sfw6660x Kuro -- 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] creating a WIX small or minor patch
The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id=RTM for PatchBaseline\@Id. PatchBaseline Id=SP3 / -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a bit more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. !-- Id must be higher than any sequence number in the baseline msi's Media/File table. Cabinet must match the original cabinet file name. -- Media Id=5728 Cabinet=Product.cab !-- Id created for the patches' baseline. Referenced in the command line. -- PatchBaseline Id=SP3 / /Media -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, RD QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email.
