Re: [WiX-users] rfc: Package element changes
Would it be possible to define a standard set of Guids which are only to be used in the qtests and have some sort of flag in your tests saying that this is a test. If this flag is not set, then get candle will treat it as an error if these guids are used? Richard Derek Cicerone wrote: Unfortunately, people treat our qtests as examples (especially given that they are categorized under the examples directory). I agree for things that are purely examples we should use the PUT-GUID-HERE thing. It’s the qtests I don't know what to do with (I really wish people wouldn't look at them but they do have the most coverage of various authoring concepts). What are your thoughts on a warning for omitting the Product/@Id attribute? Derek -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 02, 2006 10:16 AM To: [EMAIL PROTECTED]; 'Bob Arnson' Cc: 'DEÁK JAHN Gábor'; 'WiX-users'; 'Rob Mensching' Subject: RE: [WiX-users] rfc: Package element changes All examples should use PUT-GUID-HERE. You get a nice error message from the compiler and it's pretty self explanatory. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone Sent: Wednesday, August 02, 2006 8:57 AM To: 'Bob Arnson' Cc: 'DEÁK JAHN Gábor'; 'WiX-users'; 'Rob Mensching' Subject: Re: [WiX-users] rfc: Package element changes Hmm, that's a very good point. I'm just trying to address Rob's concern that a developer wouldn't understand what it means to generate the guid. Honestly, I'd be more worried about them copying a setup with a guid and failing to modify it (thus introducing collisions for users). It almost argues for us to always omit the guid in our examples in which case we'd then have to somehow educate the user that they should set a guid if they copied one of our examples. Now I'm all confused :) Derek -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Wednesday, August 02, 2006 8:44 AM To: [EMAIL PROTECTED] Cc: 'DEÁK JAHN Gábor'; 'Rob Mensching'; 'WiX-users' Subject: Re: [WiX-users] rfc: Package element changes Derek Cicerone wrote: I've done some more thinking about this. I think Rob's main objection with making Product/@Id optional was that someone might accidentally forget to specify it. However, what if we displayed a warning to the user whenever they omitted the Property/@Id attribute informing them that doing so is non-standard and would result in generating a new ProductCode for each build - thus making it impossible to do anything other than major upgrades. Why should that be a warning? -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] cab files getting corrupted
Hi, Thank you for the previous help with getting fonts to register. I have come across another problem. It seems that the files contained in the cab file Im using keep on getting corrupted. Ive tried using the MSZIP format, the LZX format and no compression at all. The files are as follows: KRB.CON 40 bytes KRB5.INI 282 bytes KRBREALM.CON 84 bytes My results as follows: MSZIP: WinRAR extracts the files correctly. After the msi has installed, each of these end up as 285 bytes each LZX: Same result as MSZIP No compression: Whole CAB file doesnt open Ive attached the wxs file just in case Im doing something wrong in that. For making the cab file Ive tried CabPack, CABARC and IExpress Thanks for any help. Simon Porter Trainee IT Engineer Heber Ltd ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi; Product Id=CCAE282F-1CD4-4E6C-A326-2A4A46A97B9A Language=2057 Manufacturer=Heber Ltd Name=Heber Keberos Settings Version=1.0.0 Package Id=F6FA744A-7119-4FD3-AF90-F3D66F8DCA45 Compressed=yes / UI / Media Id=1 Cabinet=settings.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Directory Id=WindowsFolder Name=WinDir Component Id=ConfigFiles Guid=24A1A1EE-CDBB-4D4B-94FA-8FD0F5E01DE5 File Id=KRB5 Name=KRB5.INI Vital=yes DiskId=1 Source=settings.cab / File Id=KRB Name=KRB.CON Vital=yes DiskId=1 Source=settings.cab / File Id=KRBREALM Name=KRBREALM.CON Vital=yes DiskId=1 Source=settings.cab / /Component /Directory /Directory Feature Id=ConfigFileFeature Level=1 Title=Keberos Config Files ComponentRef Id=ConfigFiles / /Feature Condition Message=You need to be an administrator to install thisPrivileged/Condition /Product /Wix Heber Ltd. Registered Office: Belvedere Mill, Chalford, Stroud, Glos, GL6 8NT, England. Registered England: 1744505 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Caching shortcut icons?
Hi Chesong, Thanks for the info. Some more testing the problem does occur with Server 2003 also. I had to replicate the pattern on XP once more to see it happening there so I think this looks like a more general problem. However, I can say that the same thing happens with ARPPRODUCTICON on XP no matter which icon I specify, the first one is in use. Server 2003 does update modifications to this property. I dont think there are workarounds for this just stick to one ARPICON and not modify it at RTM. Once again, thanks for the info. Best regards, Calin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chesong Lee Sent: Friday, August 04, 2006 11:51 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Caching shortcut icons? We have encountered the same problem. Windows Explorer is the culprit, not MSI engine. Explorer does not invalidate its icon cache even if the icon file is changed, at least in Windows XP. Refreshing icon cache can be a solution using a custom action. Although there is no known public API to refresh the shell icon cache, there is a way by changing the shell icon size (e.g. +1 or -1 of the existing value) and restoring to the old value. But this solution has a side effect that users desktop icons are rearranged. When we shipped with such custom action, we got some complaints from customers for the side effect. So we decided not to use this technique. Another solution for us was the same solution you are using changing the icon name whenever the icon data is changed we add a suffix using MD5 hash of the icon file we do this way because we supply several OEM versions of the package with custom icons and there should be an automated way to change the icon name. So far that is the only feasible way to circumvent icon cache problems for me. FYI: To achieve this, we implemented in two ways: Pre-calculate MD5 hash value of the icon and use preprocessor variable to set the icon name Build the MSI and manipulate the MSI database to add MD5 hash suffix in Name column in all rows in Icon Table. First one is easier to implement. Second is more convenient to use but it has a subtle side-effect that MSI file size grows a little bit for updating rows containing binary columns (OLE storage limitation, mentioned in MSDN). So the first one is the one we use at this time. Regards, Chesong Lee From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, August 04, 2006 4:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Caching shortcut icons? Hi List, Strange thing on Windows XP maybe you can tell me more about it. If I create a shortcut and specify an Icon, then that initial icon is displayed no matter if the icon - as a binary file - has been modified and the MSI recompiled. This is not the case with Server 2003, where the icons are properly displayed. So far it seems that changing the icon Id whenever an update on that binary is made makes XP happy. Best regards, Calin - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Control Default=yes - maybe
Hi List, An Install button may not be selected although I specified Default=yes for that Control. Looking closer at it, seems that the first button to be selected is also first button that is specified for that dialog. That would explain why a setup wizard has the Back button selected instead of Remove. Best regards, Calin - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Require License Agreement Dialog (no silent setups)
John Robbins wrote: After an hour of Googling, I can't see how to disallow silent installs. I can't see why to disallow silent installs. The default WiX installs allow you to specify \q to MSIEXEC.EXE and you get a silent install. However, that allows you to skip checking the license agreement option, which my client doesn't like. Tell your client that when someone is installing (deploying) their program to a hundreds or thousands of computers they really want to do a silent install. Bob already mentioned SMS, but also a normal Group Policy deployment method uses silent install. Breaking the msi-package with unnecessary stuff only makes system administrators angry. -- Mikko Järvinen - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixUI_Minimal without license agreement
I'm lovin' it! That's exactly what I was hoping to hear. I can put some installation notes (and maybe some positive messages) into the readme. Thanks, Brian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob ArnsonSent: Thursday, August 03, 2006 7:17 PMTo: Scott SamCc: wix-users@lists.sourceforge.netSubject: Re: [WiX-users] WixUI_Minimal without license agreement Scott Sam wrote: I want to use the Minimal wixui because I want the user to be able to just click next and have the install go, but I dont want eula in it. Is there any way to use the regular welcomeDlg in place of the WelcomeEulaDlg. I get an error 2803 when I click the next button when I tried just changing the dialogRef. What am I missing?How about a low-tech solution? Put a simple readme in License.rtf and set the LicenseAccepted property to '1' -- that enables the Install button.Otherwise, you'll need to create a new dialog; the existing WelcomeDlg is designed to be the first page in a wizard, not the last. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] audad
tribesman69.gif Description: GIF image - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] cab files getting corrupted
Simon Porter wrote: File Id="KRB5" Name="KRB5.INI" Vital="yes" DiskId="1" Source="settings.cab" / File Id="KRB" Name="KRB.CON" Vital="yes" DiskId="1" Source="settings.cab" / File Id="KRBREALM" Name="KRBREALM.CON" Vital="yes" DiskId="1" Source="settings.cab" / That creates three files in your setup, all of which contain the contents of settings.cab. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] MessageQueue PubCA
I am getting the following [CANDLE] error [CNDL0005] from my WiX Fragment file that configures as Microsoft Message Queue. I get the same error whether I use the MessageQueue element (with / without an in-element xmlns attribute definition) or pca:MessageQueue element (with / without an xmlns:pca attribute definition in the outer WiX element. I notice that the element is not available via Intellisense in VS.NET (using Votive). I am running WiX / Votive v.2.0.4421.0 VS.NET v1.1 / v2.0. Error Message: d:\MYFOLDER\CMQ.Common.wxs(10) : error CNDL0005 : The Component element contains an unexpected child element 'MessageQueue'. ... Fragment User Id=ntwkService Domain=NT AUTHORITY Name=NETWORK SERVICE / DirectoryRef Id=TARGETDIR Component Id=CreateMessageQueue Guid=AC1B0EAE-905D-4532-99D1-400FBA70799D MessageQueue xmlns=http://schemas.microsoft.com/wix/2005/02/pubca; Id=mQ Label=RiskTech Interfaces Message Queue PathName=.\Private$\rtiQ MessageQueuePermission Id=permissionNetworkService User=ntwkService PeekMessage=yes ReceiveMessage=yes WriteMessage=yes / /MessageQueue /Component /DirectoryRef Feature Id=MsgQueue Level=1 Title=Message Queue Description=Creates Private Message Queue ComponentRef Id=CreateMessageQueue / /Feature /Fragment ... David Adams MSN MessengerID: [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Control Default=yes - maybe
Calin Iaru wrote: An Install button may not be selected although I specified Default=yes for that Control. Looking closer at it, seems that the first button to be selected is also first button that is specified for that dialog. That would explain why a setup wizard has the Back button selected instead of Remove. In the case of WixUI, at least, that's intentional. Default buttons shouldn't have "destructive" behavior. I use control conditions in VerifyReadyDlg to show the Remove button and then make Back the default. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MessageQueue PubCA
From Fredrik Grohn [EMAIL PROTECTED] mail You need to include the PubCA compiler extension on the command line. Here is an example: candle queues.wxs -ext Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext When you link it you also need to include pubca.wixlib: light queues.wixobj %WIX_HOME%\ca\pubca.wixlib -out queues.msi -ext Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext (%WIX_HOME% is the directory where you have WiX installed on you system.) - Chandra -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone Sent: Friday, August 04, 2006 12:33 PM To: 'david adams'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MessageQueue PubCA You need to pass in the pubca extension. For v2, it should look something like this: -ext assembly, class (or maybe its class, assembly - I don't remember - it was always too verbose for me :) (I'm not sure of the specifics for pubca unfortunately - perhaps a fellow dev can help out here). Derek -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Friday, August 04, 2006 12:23 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MessageQueue PubCA Derek: d:\program files\windows installer xml\bin\candle d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\crawford.risktech.interfaces.wxs d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\crawford.risktech.class.library.wxs d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\cwa.common.wxs d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\cwd.anonymousauth.wxs d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\cdx.impersonations.wxs d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\cmq.common.wxs I am getting the error in the last *.wxs file that was created (cmq.common.wxs). David Adams MSN MessengerID: [EMAIL PROTECTED] From: Derek Cicerone [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: 'david adams' [EMAIL PROTECTED],wix-users@lists.sourceforge.net Subject: RE: [WiX-users] MessageQueue PubCA Date: Fri, 4 Aug 2006 08:29:09 -0700 MIME-Version: 1.0 Received: from winisp-fe1.winisp.net ([192.197.157.82]) by bay0-mc4-f15.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Fri, 4 Aug 2006 08:29:12 -0700 Received: from derekclap ([67.168.109.53]) by winisp-fe1.winisp.net over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 Aug 2006 08:29:11 -0700 X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlKtU9j2Z7TuGo= X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aca31W62MXvabLltSXSP4lp+t2VLjQABRJBw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2922 Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 04 Aug 2006 15:29:12.0012 (UTC) FILETIME=[BC8368C0:01C6B7DA] What does your command line look like for candle? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Friday, August 04, 2006 7:51 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] MessageQueue PubCA I am getting the following [CANDLE] error [CNDL0005] from my WiX Fragment file that configures as Microsoft Message Queue. I get the same error whether I use the MessageQueue element (with / without an in-element xmlns attribute definition) or pca:MessageQueue element (with / without an xmlns:pca attribute definition in the outer WiX element. I notice that the element is not available via Intellisense in VS.NET (using Votive). I am running WiX / Votive v.2.0.4421.0 VS.NET v1.1 / v2.0. Error Message: d:\MYFOLDER\CMQ.Common.wxs(10) : error CNDL0005 : The Component element contains an unexpected child element 'MessageQueue'. ... Fragment User Id=ntwkService Domain=NT AUTHORITY Name=NETWORK SERVICE / DirectoryRef Id=TARGETDIR Component Id=CreateMessageQueue Guid=AC1B0EAE-905D-4532-99D1-400FBA70799D MessageQueue xmlns=http://schemas.microsoft.com/wix/2005/02/pubca; Id=mQ Label=RiskTech Interfaces Message Queue PathName=.\Private$\rtiQ MessageQueuePermission Id=permissionNetworkService User=ntwkService PeekMessage=yes ReceiveMessage=yes WriteMessage=yes / /MessageQueue /Component /DirectoryRef Feature Id=MsgQueue Level=1 Title=Message Queue Description=Creates Private Message Queue ComponentRef Id=CreateMessageQueue / /Feature /Fragment ... David Adams MSN MessengerID: [EMAIL PROTECTED] --- -- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVD EV
[WiX-users] Shortcuts orphaned when changed out from under File
Based on an earlier email reply(8/1/2006 subject=Shortcuts) from Derek. In this reply Derek suggested that shortcuts should not always be definedunder the File but independently because shortcuts and ALLUSERS don't always coexist in a manner that makes sense. Some relevant facts on the *.wxs: Wix being used = v2 (wix_2.0.3719.0) Install sets ALLUSERS property to 1. Product ID and Package ID are changed with each release. and InstallExecuteSequence RemoveExistingProducts After='InstallFinalize' / /InstallExecuteSequence So I took all my shortcuts out from within the File elements and placed them within their own component elements. When this new MSI is run on a workstation that has any previous install on it the old shortcuts (desktop and startmenu) are left on the machine along side the new shortcuts. Why were the old shortcuts not removed? Dave WilliamsonClear Sky Software704.568.5544 sales704.554.6300 support704.943.0585 fax[EMAIL PROTECTED]www.clearskysoftware.com - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcuts orphaned when changed out from under File
non-advertised shortcuts Have not delved into ICE validation yet ... see a little too much bantering back and forth about what is "passing ICE validation". I'm too much of a newbie yet. Dave WilliamsonClear Sky Software704.568.5544 sales704.554.6300 support704.943.0585 fax[EMAIL PROTECTED]www.clearskysoftware.com From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Derek CiceroneSent: Friday, August 04, 2006 4:38 PMTo: 'Dave Williamson'; wix-users@lists.sourceforge.netSubject: Re: [WiX-users] Shortcuts orphaned when changed out from under File Are you using advertised or non-advertised shortcuts? Did your MSI pass ICE validation? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave WilliamsonSent: Friday, August 04, 2006 1:20 PMTo: wix-users@lists.sourceforge.netSubject: [WiX-users] Shortcuts orphaned when changed out from under File Based on an earlier email reply(8/1/2006 subject=Shortcuts) from Derek. In this reply Derek suggested that shortcuts should not always be definedunder the File but independently because shortcuts and ALLUSERS don't always coexist in a manner that makes sense. Some relevant facts on the *.wxs: Wix being used = v2 (wix_2.0.3719.0) Install sets ALLUSERS property to 1. Product ID and Package ID are changed with each release. and InstallExecuteSequence RemoveExistingProducts After='InstallFinalize' / /InstallExecuteSequence So I took all my shortcuts out from within the File elements and placed them within their own component elements. When this new MSI is run on a workstation that has any previous install on it the old shortcuts (desktop and startmenu) are left on the machine along side the new shortcuts. Why were the old shortcuts not removed? Dave WilliamsonClear Sky Software704.568.5544 sales704.554.6300 support704.943.0585 fax[EMAIL PROTECTED]www.clearskysoftware.com - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MessageQueue PubCA
It appears that Fredrik had already answered the question. When I looked on the SourceForge Wix-Users archive, I found the following: **Cliff Notes version from Fredrik's email candle queues.wxs -ext Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext light queues.wixobj %WIX_HOME%\ca\pubca.wixlib -out queues.msi -ext Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext (%WIX_HOME% is the directory where you have WiX installed on you system.) *** When I took the steps, it appears that I am missing the pcaext.dll for the reference and the pubca.wixlib. Are these not available in the bin directory like wixca, etc.? David Adams MSN MessengerID: [EMAIL PROTECTED] From: Derek Cicerone [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: 'david adams' [EMAIL PROTECTED],wix-users@lists.sourceforge.net Subject: RE: [WiX-users] MessageQueue PubCA Date: Fri, 4 Aug 2006 12:32:59 -0700 MIME-Version: 1.0 Received: from winisp-fe1.winisp.net ([192.197.157.82]) by bay0-mc5-f6.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Fri, 4 Aug 2006 12:33:00 -0700 Received: from derekclap ([131.107.0.89]) by winisp-fe1.winisp.net over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 Aug 2006 12:32:59 -0700 X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlKtU9j2Z7TuGo= X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aca3+2B7nwCLXwMGSka2Q4fxhiOZUAAAQKBA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2922 Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 04 Aug 2006 19:32:59.0464 (UTC) FILETIME=[CB277480:01C6B7FC] You need to pass in the pubca extension. For v2, it should look something like this: -ext assembly, class (or maybe its class, assembly - I don't remember - it was always too verbose for me :) (I'm not sure of the specifics for pubca unfortunately - perhaps a fellow dev can help out here). Derek -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Friday, August 04, 2006 12:23 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MessageQueue PubCA Derek: d:\program files\windows installer xml\bin\candle d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\crawford.risktech.interfaces.wxs d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\crawford.risktech.class.library.wxs d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\cwa.common.wxs d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\cwd.anonymousauth.wxs d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\cdx.impersonations.wxs d:\development\vs2003\services\rti\risktechinterfaces\risktech interfaces wix install\cmq.common.wxs I am getting the error in the last *.wxs file that was created (cmq.common.wxs). David Adams MSN MessengerID: [EMAIL PROTECTED] From: Derek Cicerone [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: 'david adams' [EMAIL PROTECTED],wix-users@lists.sourceforge.net Subject: RE: [WiX-users] MessageQueue PubCA Date: Fri, 4 Aug 2006 08:29:09 -0700 MIME-Version: 1.0 Received: from winisp-fe1.winisp.net ([192.197.157.82]) by bay0-mc4-f15.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Fri, 4 Aug 2006 08:29:12 -0700 Received: from derekclap ([67.168.109.53]) by winisp-fe1.winisp.net over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 Aug 2006 08:29:11 -0700 X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlKtU9j2Z7TuGo= X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aca31W62MXvabLltSXSP4lp+t2VLjQABRJBw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2922 Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 04 Aug 2006 15:29:12.0012 (UTC) FILETIME=[BC8368C0:01C6B7DA] What does your command line look like for candle? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Friday, August 04, 2006 7:51 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] MessageQueue PubCA I am getting the following [CANDLE] error [CNDL0005] from my WiX Fragment file that configures as Microsoft Message Queue. I get the same error whether I use the MessageQueue element (with / without an in-element xmlns attribute definition) or pca:MessageQueue element (with / without an xmlns:pca attribute definition in the outer WiX element. I notice that the element is not available via Intellisense in VS.NET (using Votive). I am running WiX / Votive v.2.0.4421.0 VS.NET v1.1 / v2.0. Error Message: d:\MYFOLDER\CMQ.Common.wxs(10) : error CNDL0005 : The Component element contains an unexpected child element 'MessageQueue'. ... Fragment User Id=ntwkService Domain=NT AUTHORITY Name=NETWORK SERVICE / DirectoryRef Id=TARGETDIR Component Id=CreateMessageQueue
Re: [WiX-users] Shortcuts orphaned when changed out from under File
Derek Cicerone wrote: Non-advertised shortcuts require dummy HKCU keypaths in their components – do you have those? (This is one of many mistakes ICE validation catches) The OP is using ALLUSERS=1 so that would make the problem worse, not better (modifying HKCU in ALLUSERS would mean that the only the admin that installed it could uninstall it...) It's probably not changing the component GUIDs - you have to change them when you change a component (and probably force a major upgrade so the old ones are uninstalled just to be safe) otherwise it thinks that nothing has changed and doesn't install the new ones. Tony - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FW: Re: MessageQueue PubCA
Justin or Bob would have to answer that question - I'm not sure what Votive installs these days :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Friday, August 04, 2006 2:07 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] FW: Re: MessageQueue PubCA I downloaded the 2.0.4421.0 binaries and retrieved the pubca.wixlib pcaext.dll files. The install generated the MSI. Thanks Derek. BTW. Should the wixlib dll have been installed with the Votive install? David Adams MSN MessengerID: [EMAIL PROTECTED] From: david adams [EMAIL PROTECTED] To: [EMAIL PROTECTED], wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MessageQueue PubCA Date: Fri, 04 Aug 2006 20:42:59 + MIME-Version: 1.0 X-Originating-IP: [12.6.40.2] X-Originating-Email: [EMAIL PROTECTED] X-Sender: [EMAIL PROTECTED] Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc6-f7.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Fri, 4 Aug 2006 13:43:12 -0700 Received: from sc8-sf-list1-new.sourceforge.net (unknown [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 2B8AC12F35; Fri, 4 Aug 2006 13:43:12 -0700 (PDT) Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1G96Vh-Fe-OYfor wix-users@lists.sourceforge.net; Fri, 04 Aug 2006 13:43:09 -0700 Received: from bay0-omc1-s8.bay0.hotmail.com ([65.54.246.80])by mail.sourceforge.net with esmtp (Exim 4.44) id 1G96Vh-0008Af-9Efor wix-users@lists.sourceforge.net; Fri, 04 Aug 2006 13:43:09 -0700 Received: from hotmail.com ([64.4.61.24]) by bay0-omc1-s8.bay0.hotmail.comwith Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 Aug 2006 13:43:04 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;Fri, 4 Aug 2006 13:43:03 -0700 Received: from 64.4.61.200 by by102fd.bay102.hotmail.msn.com with HTTP;Fri, 04 Aug 2006 20:42:59 GMT X-Message-Info: txF49lGdW41un/J1DbPfyfIVh5GhNQ0qo3EKQvRVlr8= X-OriginalArrivalTime: 04 Aug 2006 20:43:03.0602 (UTC)FILETIME=[95040120:01C6B806] X-Spam-Score: 0.5 (/) X-Spam-Report: Spam Filtering performed by sourceforge.net.See http://spamassassin.org/tag/ for more details.Report problems tohttp://sf.net/tracker/?func=addgroup_id=1atid=210.5 FROM_ENDS_IN_NUMS From: ends in numbers0.0 MSGID_FROM_MTA_HEADER Message-Id was added by a relay X-BeenThere: wix-users@lists.sourceforge.net X-Mailman-Version: 2.1.8 Precedence: list List-Id: General discussion for Windows Installer XML toolset.wix-users.lists.sourceforge.net List-Unsubscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:wix-users- [EMAIL PROTECTED] List-Archive: http://sourceforge.net/mailarchive/forum.php?forum=wix-users List-Post: mailto:wix-users@lists.sourceforge.net List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:wix-users- [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] It appears that Fredrik had already answered the question. When I looked on the SourceForge Wix-Users archive, I found the following: **Cliff Notes version from Fredrik's email candle queues.wxs -ext Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext light queues.wixobj %WIX_HOME%\ca\pubca.wixlib -out queues.msi -ext Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext (%WIX_HOME% is the directory where you have WiX installed on you system.) *** When I took the steps, it appears that I am missing the pcaext.dll for the reference and the pubca.wixlib. Are these not available in the bin directory like wixca, etc.? David Adams MSN MessengerID: [EMAIL PROTECTED] From: Derek Cicerone [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: 'david adams' [EMAIL PROTECTED],wix-users@lists.sourceforge.net Subject: RE: [WiX-users] MessageQueue PubCA Date: Fri, 4 Aug 2006 12:32:59 -0700 MIME-Version: 1.0 Received: from winisp-fe1.winisp.net ([192.197.157.82]) by bay0-mc5-f6.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Fri, 4 Aug 2006 12:33:00 -0700 Received: from derekclap ([131.107.0.89]) by winisp-fe1.winisp.net over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 Aug 2006 12:32:59 -0700 X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlKtU9j2Z7TuGo= X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aca3+2B7nwCLXwMGSka2Q4fxhiOZUAAAQKBA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2922 Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 04 Aug 2006 19:32:59.0464 (UTC) FILETIME=[CB277480:01C6B7FC] You need to pass in the pubca extension. For v2, it should look something like this: -ext assembly, class (or maybe its class, assembly - I don't remember - it was always too verbose for me :) (I'm not sure of the specifics for pubca
Re: [WiX-users] FW: Re: MessageQueue PubCA
Justin Rockwood wrote: Yes, they should be installed with Votive but they're currently not. Bob has been working on a fix for that, but it's not in yet. Yeah, it's been a low priority while Votive is in such active development. When Justin does his next big checkin, the setup will be updated to match. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
