[WiX-users] dynamically fill a combobox
Hi, I want to use a custom action to fill dynamically a combobox. But I do not know how the output of the custom action should look like. I only think to know that I have to bind a property to the ouput to get the selected item of the combobox. Regards, Peter - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Fw: Some STUPID Limitations in WiX
Bob Arnson wrote: It will update the shared component but it won't update the other product, so a repair operation can undo the patch. That's why merge modules are falling way out of favor... Hello Bob, Thanks for your clarification. It seems I will have to adress all the products using the MSM with my patch. Fortunatelly this would be possible because all the products using my MSM are well-known to me (my MSM is not world-wide released - it is used only by my company's products). However, not all these products are using WIX so I do not have wixpdbs from their releases = I do not have wixmsts for all of them to send to pyro. However, all the product codes and any other potentially usefull informations are available to me. More, my product for which I have wixpdbs is localized (I have multiple MSIs), but the patches I shall deliver will not be localized, so I would like to build a patch using only one set of differences, no matter how many language-dependent versions I have. So far I don't know how to instruct pyro to address my patch to all MSIs unless I make differences for all of them and pass all these difference sets to pyro. Can you please advice me if it's possible to target multiple MSIs with only one set of differences and how ? Regards, Cristian - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Driver installation linker error
I am trying to install a driver using Wix 3.0 and DifxAppExtension. When I build my installer I get this linker error: Unresolved reference to symbol 'CustomAction:MsiProcessDrivers' My Wix source code is shown below. Can anyone help me find out how to avoid this linker error? Thanks Bo ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:difx=http://schemas.microsoft.com/wix/DifxAppExtension; Product Id=c2bf8f6e-ff84-4b27-adc8-4acc9486cfd3 Name=My Driver Language=1033 Version=1.0.0.0 Manufacturer=My Company UpgradeCode=ad6ba1b3-686a-4f49-8c52-84fe1c389d50 Package InstallerVersion=200 Compressed=yes / Property Id=ALLUSERS1/Property Media Id=1 Cabinet=DriverInstallation.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Component Id=ProductComponent Guid=3e0aa007-4463-4f70-aaf2-ad9c1feffb8c difx:Driver AddRemovePrograms=no Legacy=yes PlugAndPlayPrompt=no / File Id=MyDriver.sys Name=MyDriver.sys Source=MyDriver.sys / File Id=MyDriver.inf Name=MyDriver.inf Source=MyDriver.inf / /Component /Directory Feature Id=ProductFeature Title=My Driver Feature Level=1 ComponentRef Id=ProductComponent / /Feature /Product /Wix -- View this message in context: http://www.nabble.com/Driver-installation-linker-error-tf4553810.html#a12995389 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Driver installation linker error
I am trying to install a driver using Wix 3.0 and DifxAppExtension. When I build my installer I get this linker error: Unresolved reference to symbol 'CustomAction:MsiProcessDrivers' My Wix source code is shown below. Can anyone help me find out how to avoid this linker error? Thanks Bo ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:difx=http://schemas.microsoft.com/wix/DifxAppExtension; Product Id=c2bf8f6e-ff84-4b27-adc8-4acc9486cfd3 Name=My Driver Language=1033 Version=1.0.0.0 Manufacturer=My Company UpgradeCode=ad6ba1b3-686a-4f49-8c52-84fe1c389d50 Package InstallerVersion=200 Compressed=yes / Property Id=ALLUSERS1/Property Media Id=1 Cabinet=DriverInstallation.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Component Id=ProductComponent Guid=3e0aa007-4463-4f70-aaf2-ad9c1feffb8c difx:Driver AddRemovePrograms=no Legacy=yes PlugAndPlayPrompt=no / File Id=MyDriver.sys Name=MyDriver.sys Source=MyDriver.sys / File Id=MyDriver.inf Name=MyDriver.inf Source=MyDriver.inf / /Component /Directory Feature Id=ProductFeature Title=My Driver Feature Level=1 ComponentRef Id=ProductComponent / /Feature /Product /Wix -- View this message in context: http://www.nabble.com/Driver-installation-linker-error-tf4553811.html#a12995390 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Latest nightly build (3.0.3328.0) seems to be broken
The latest nightly build, version 3.0.3328.0, seems to be broken - specifically there seems to be a problem with the strong name signing: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'wix, Version=3.0.3328.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'wix, Version=3.0.3328.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad' Assembly manager loaded from: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll Running under executable c:\Projects\wix\3.0.3328.0\bin\candle.exe --- A detailed error log follows. === Pre-bind state information === LOG: User = OPTIONEXIST\john LOG: DisplayName = wix, Version=3.0.3328.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad (Fully-specified) LOG: Appbase = file:///c:/Projects/wix/3.0.3328.0/bin/ file:///c:/Projects/wix/3.0.3328.0/bin/ LOG: Initial PrivatePath = NULL Calling assembly : candle, Version=3.0.3328.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad. === LOG: This bind starts in default load context. LOG: Using application configuration file: c:\Projects\wix\3.0.3328.0\bin\candle.exe.Config LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config. LOG: Post-policy reference: wix, Version=3.0.3328.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad LOG: Attempting download of new URL file:///c:/Projects/wix/3.0.3328.0/b file:///c:/Projects/wix/3.0.3328.0/b file:///c:/Projects/wix/3.0.3328.0/bin/wix.DLL in/wix.DLL. WRN: Comparing the assembly name resulted in the mismatch: PUBLIC KEY TOKEN ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated. Regards, John - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Explanation for why you can't have both a 32-bit and 64-bit installer
What you can do with MSI : - create an installer which will install Win32 components on Win32 platforms - create an installer which will install x64 and/or Win32 components on x64 platforms You can't however create a single MSI for both Win32 and x64 platforms. Because a MSI must be specified as for Win32 or for x64. The Win32 MSI will be installed on a x64 platform (but can install only Win32 components). The x64 MSI will NOT run on Win32 platforms. You will have to create separate Win32 and x64 MSIs (at best, the x64 MSI can install both Win32 and x64 components). Nothing to do with WiX - these are basic limitations of Windows Installer. - Original Message From: OneReallyCoolApplication [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Monday, October 1, 2007 7:08:06 PM Subject: [WiX-users] Explanation for why you can't have both a 32-bit and 64-bit installer I am supposed to create a MSI package using WiX that can detect whether the computer it's on has 32-bit or 64-bit architecture, and install different files for each. I have browsed Nabble and found replies that say making a single installer that does this is impossible, such as these: http://www.nabble.com/32-and-64-bit-installer-in-one-tf2635209.html http://www.nabble.com/64-bit-newbie-question-tf3979370.html However my boss is not satisfied with this explanation and wants a detailed technical explanation of why WiX or Windows Installer cannot do this. Could any of you give this explanation or perhaps suggest an alternative that I could do? Any links to outside sources would be great, since I suspect my boss doesn't trust Nabble much. Thanks in advance for your help. -- View this message in context: http://www.nabble.com/Explanation-for-why-you-can%27t-have-both-a-32-bit-and-64-bit-installer-tf4549274.html#a12982169 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Catch up on fall's hot new shows on Yahoo! TV. Watch previews, get listings, and more! http://tv.yahoo.com/collections/3658 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Explanation for why you can't have both a 32-bitand 64-bit installer
Presumably though, one can have an x64 and an x86 MSI, and a boot-strapper that detects architecture and runs the correct MSI? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Gantoi Sent: 02 October 2007 14:54 To: OneReallyCoolApplication; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Explanation for why you can't have both a 32-bitand 64-bit installer What you can do with MSI : - create an installer which will install Win32 components on Win32 platforms - create an installer which will install x64 and/or Win32 components on x64 platforms You can't however create a single MSI for both Win32 and x64 platforms. Because a MSI must be specified as for Win32 or for x64. The Win32 MSI will be installed on a x64 platform (but can install only Win32 components). The x64 MSI will NOT run on Win32 platforms. You will have to create separate Win32 and x64 MSIs (at best, the x64 MSI can install both Win32 and x64 components). Nothing to do with WiX - these are basic limitations of Windows Installer. - Original Message From: OneReallyCoolApplication [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Monday, October 1, 2007 7:08:06 PM Subject: [WiX-users] Explanation for why you can't have both a 32-bit and 64-bit installer I am supposed to create a MSI package using WiX that can detect whether the computer it's on has 32-bit or 64-bit architecture, and install different files for each. I have browsed Nabble and found replies that say making a single installer that does this is impossible, such as these: http://www.nabble.com/32-and-64-bit-installer-in-one-tf2635209.html http://www.nabble.com/64-bit-newbie-question-tf3979370.html However my boss is not satisfied with this explanation and wants a detailed technical explanation of why WiX or Windows Installer cannot do this. Could any of you give this explanation or perhaps suggest an alternative that I could do? Any links to outside sources would be great, since I suspect my boss doesn't trust Nabble much. Thanks in advance for your help. -- View this message in context: http://www.nabble.com/Explanation-for-why-you-can%27t-have-both-a-32-bit-and-64-bit-installer-tf4549274.html#a12982169 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Shape Yahoo! in your own image. Join our Network Research Panel today!http://us.rd.yahoo.com/evt=48517/*http:/surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 -- This message has been scanned for viruses by Sophos PureMessage. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Explanation for why you can't have both a 32-bitand 64-bit installer
Presumably though, one can have an x64 and an x86 MSI, and a boot-strapper that detects architecture and runs the correct MSI? Yes, definitely. John - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Explanation for why you can't have both a 32-bit and 64-bit installer
The MSDN Windows Installer documentation should be sufficient to explain this limitation. I'd start here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/windows_installer_on_64_bit_operating_systems.asp http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/using_64-bit_windows_installer_packages.asp I think the key is that you can't have components that install to the 64-bit locations unless the package is specifically marked as a 64-bit package. Once the package is marked that way, you won't be able to run it on a 32-bit system. Dana On 10/2/07, Adrian Gantoi [EMAIL PROTECTED] wrote: What you can do with MSI : - create an installer which will install Win32 components on Win32 platforms - create an installer which will install x64 and/or Win32 components on x64 platforms You can't however create a single MSI for both Win32 and x64 platforms. Because a MSI must be specified as for Win32 or for x64. The Win32 MSI will be installed on a x64 platform (but can install only Win32 components). The x64 MSI will NOT run on Win32 platforms. You will have to create separate Win32 and x64 MSIs (at best, the x64 MSI can install both Win32 and x64 components). Nothing to do with WiX - these are basic limitations of Windows Installer. - Original Message From: OneReallyCoolApplication [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Monday, October 1, 2007 7:08:06 PM Subject: [WiX-users] Explanation for why you can't have both a 32-bit and 64-bit installer I am supposed to create a MSI package using WiX that can detect whether the computer it's on has 32-bit or 64-bit architecture, and install different files for each. I have browsed Nabble and found replies that say making a single installer that does this is impossible, such as these: http://www.nabble.com/32-and-64-bit-installer-in-one-tf2635209.html http://www.nabble.com/64-bit-newbie-question-tf3979370.html However my boss is not satisfied with this explanation and wants a detailed technical explanation of why WiX or Windows Installer cannot do this. Could any of you give this explanation or perhaps suggest an alternative that I could do? Any links to outside sources would be great, since I suspect my boss doesn't trust Nabble much. Thanks in advance for your help. -- View this message in context: http://www.nabble.com/Explanation-for-why-you-can%27t-have-both-a-32-bit-and-64-bit-installer-tf4549274.html#a12982169 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Shape Yahoo! in your own image. Join our Network Research Panel today!http://us.rd.yahoo.com/evt=48517/*http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Explanation for why you can't have both a 32-bit and 64-bit installer
OneReallyCoolApplication wrote: I am supposed to create a MSI package using WiX that can detect whether the computer it's on has 32-bit or 64-bit architecture, and install different files for each. I believe that this is possible (using the VersionNT64 property) *provided you're not trying to install 64-bit files or install into the 64-bit-specific parts of the registry or file-system*. As soon as you need to start making 64-bit reg/file-system changes then you need a 64-bit MSI, and of course this won't run on 32-bit windows. It *is* possible to conditionally compile a 32- or 64-bit MSI from a single set of source, but you need to be careful with things like component codes. -- View this message in context: http://www.nabble.com/Explanation-for-why-you-can%27t-have-both-a-32-bit-and-64-bit-installer-tf4549274.html#a12999699 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Release 3.0.3328.0 Assemblies won't bind
Hi, I get the following error when running the Candle.exe in the WiX Release 3.0.3328.0 : Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'wix, Version=3.0.3328.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'wix, Version=3.0.3328.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad' I suspect it's caused by the recent Strong Name changes made by PMarcu, because Release 3.0.3307.0 doesn't give any such problems, and the candle.exe.config in that file has significantly less in it. Or I could be completely wrong... Please advise if you want a bug raised. Regards Martin. _ The information contained in this message, together with any attachments, may be legally privileged or confidential and is intended only for the use of the individual(s) or entity named above. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately before deleting it. This message has been checked for all known viruses through MessageLabs Virus Control Centre, for and on behalf of the AVEVA Group. Although no viruses were found it is the recipient's responsibility to ensure that this message is safe for use on their system. AVEVA Group plc is a Public Limited Company registered in England with registered number 2937296. The registered office of AVEVA Group plc is High Cross, Madingley Road, Cambridge, England CB3 0HB- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] no tallow in wix 3.0
Hi. How come there's no tallow utility in Wix 3.0 binaries? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Embedded locale transforms
Okay I figured it out... you need to ommit the transform's file extension. In my example, just call the file 1036 and embed this. -- View this message in context: http://www.nabble.com/Embedded-locale-transforms-tf4523004.html#a13001287 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Reference one directory up.
How do you specify where your files are located when you don't want to hard code the directory, just have it point to one directory up? Thanks in advance. -- Jessica Darling - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE03 error from light
Massive thanks guys for your help ... in the end it was a simple spelling error
which didn't show up in the compile stage...
The additional information and guidance (such as using Orca) certainly
helped to tie it down and will be very useful going forward,
Also the -sice:ICE03 flag does suppress the error so no worries there!
Thanks again,
Dave
-Original Message-
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: 01 October 2007 22:22
To: 'Peter Marcu'; Ogborne, Dave; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] ICE03 error from light
You need to spell out completely the name of the ICE to suppress:
-sice:ICE03
DllPath is not meant to be a foreign key reference column according to
src\ext\ComPlusExtension\wixext\data\tables.xml! The keyTable and keyColumn
attributes are not specified. In this error message, isn't LAComPlusAssembly
the value of the key column(s) for the row that was considered to be in
error, rather than the actual erroneous data?
Is the _Validation table being generated incorrectly? Could you try running
light with -sval and examine the _Validation table with Orca? You're looking
for a row where Table=ComPlusAssembly and Column=DllPath. According to the
definition in tables.xml, Nullable should be 'Y', MinValue, MaxValue,
KeyTable and KeyColumn should be null, Category should be 'Formatted' and
the other two fields also null.
There clearly _is_ some problem with one of the parameters - the error in
the log starts 0x8007, so is a FACILITY_WIN32 error, and it's
ERROR_INVALID_PARAMETER.
I don't think we can provide much more help without seeing the source.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter Marcu
Sent: 01 October 2007 17:59
To: daveog; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] ICE03 error from light
The error is saying that the DllPath column of the ComPlusAssembly table has
a value of LAPComPlusAssembly. This is a foreign key and therefore needs to
be present in the table has the corresponding primary key. Make sure that
LAPComPlusAssembly is defined as a Primary key somewhere else in your msi. I
cant see the code right now to tell you exactly which table needs to have
that Primary key defined.
Also, -sice:03 should suppress ice03 from being run. If it doesn’t, that’s a
bug that we should fix.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of daveog
Sent: Monday, October 01, 2007 8:42 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] ICE03 error from light
Hi all,
I am seeing the following error from the linking phase:
error LGHT0204 : ICE03: Not a valid foreign key; Table: ComPlusAssembly,
Column: DllPath, Key(s): LAPComPlusAssembly
Binder temporary directory located at 'C:\Documents and
Settings\dogborne\Local Settings\Temp\1lro9s9v'.
Validator temporary directory located at 'C:\Documents and
Settings\dogborne\Local Settings\Temp\7zjin2ut'.
using the following link command:
light -ext wixcomplusextension -cultures:en-us
letterproductioninstall.wixobj keywordrestrict.wixobj -out
keywordrestrict.msi
Microsoft (R) Windows Installer Xml Linker version 3.0.3328.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
I have tried using the -notidy and -sice switches but the error is still
produced!
A resulting msi is produced but when I run it I get the following msi
errors:
MSI (s) (78:20) [16:10:46:725]: The call to SRSetRestorePoint API failed.
Returned status: 0. GetLastError() returned: 127
and further down the log file ...
MSI (s) (78:20) [16:10:48:157]: Executing op:
CustomActionSchedule(Action=ComPlusRollbackInstallExecute,ActionType=3329,So
urce=BinaryData,Target=ComPlusRollbackInstallExecute,CustomActionData=C:\DOC
UME~1\dogborne\LOCALS~1\Temp\CPI63E1E26B.tmp€CreateSubscriptionsComPlusCompo
nents€Creating
subscriptions for COM+ components€Subscription:
[1]€0€AddComPlusRoleAssignments€Assigning roles to COM+
components€Component: [1]€0€RegisterComPlusAssemblies€Registering COM+
components€DLL:
[1]€1€2€5€LAPComPlusAssembly€0€{DA3AA263-8D65-4466-A610-2A6E45CC4B9F
}€€5€{D419CE6F-42D6-45D1-B451-6E66F40D2FD9}€0€0€0€{80E7D5F7-28E8-4180-8C65-5
C90C606EB33}€0€0€0€{52DCCE25-40DF-4DEF-AF33-1279DC230C0E}€0€0€0€{24538838-CC
96-4F50-89D8-DC5CE1E6FB52}€0€0€0€{0B737682-CC88-472F-AE9B-A39DE0B982AC}€0€0€
0€AddUsersToComPlusApplicationRoles€Adding
users to COM+ application roles€User:
[1]€0€CreateComPlusApplicationRoles€Creating COM+ application roles€Role:
[1]€0€CreateComPlusApplications€Creating COM+ applications€Application:
[1]€1€2€1€CISSLAPDLLCOMPLUS€{DA3AA263-8D65-4466-A610-2A6E45CC4B9F}€Lette
r
And Phrase
MSI (s) (78:20) [16:10:48:157]: Executing op:
ActionStart(Name=ComPlusInstallExecute,Description=Registering COM+
components,)
MSI (s) (78:20) [16:10:48:157]: Executing op:
CustomActionSchedule(Action=ComPlusInstallExecute,ActionType=3073,Source=Bin
Re: [WiX-users] no tallow in wix 3.0
Tallow doesn't exist in WiX 3.0. Take a look at Heat. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sergei Shelukhin Sent: Tuesday, October 02, 2007 8:36 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] no tallow in wix 3.0 Hi. How come there's no tallow utility in Wix 3.0 binaries? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] no tallow in wix 3.0
It's been replaced by a similar tool called heat. rrraven wrote: Hi. How come there's no tallow utility in Wix 3.0 binaries? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/no-tallow-in-wix-3.0-tf474.html#a13001575 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] no tallow in wix 3.0
Use heat.exe instead On 02/10/2007, Sergei Shelukhin [EMAIL PROTECTED] wrote: Hi. How come there's no tallow utility in Wix 3.0 binaries? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reference one directory up.
..\ is the syntax for one folder up from the current folder. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jessi Darling Sent: Tuesday, October 02, 2007 8:47 AM To: wix-users Subject: [WiX-users] Reference one directory up. How do you specify where your files are located when you don't want to hard code the directory, just have it point to one directory up? Thanks in advance. -- Jessica Darling - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom UI help
Anidil wrote: and UIRef Id=My_WixUI_InstallDir / in the WiX installer source file. and i add My_WixUI_InstallDir.wixlib,which is a custom library to the light command line, and have followed the instructions given in the WiX tutorial to create custom library.. I get the same error though.any comments? The error is saying it can't find it so I'd look at your .wixlib. Or just add it to your project as another .wxs file. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Flag or Property for Remove
Srinivas Tirupati wrote: Biut this is not working How? -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [WiX-commits] Wix 2 and service
Gonzalo Diethelm wrote: The only reason not to use ServiceInstall and ServiceControl is the DRY principle (Don't Repeat Yourself).Since I MUST provide a way for users to start/stop/install/delete the service from the console, I don't want to replicate that mechanism anywhere else, hence the very simple actions in a DLL that invoke these operations. Both DRY and Occam's Razor include the term unnecessarily. Correctly handling service installation isn't simple, so this is a case where repeating the information has value. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fw: Some STUPID Limitations in WiX
Cristian Baiu wrote: So far I don't know how to instruct pyro to address my patch to all MSIs unless I make differences for all of them and pass all these difference sets to pyro. Can you please advice me if it's possible to target multiple MSIs with only one set of differences and how ? You'll need to use Torch's -ax switch to use admin images. I'm not sure how well that works to create one patch that also targets products using .wixpdbs. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Attaching Condition to a CA from Merge Module
Ben Greenberg wrote: But, since MsiProcessDrivers is declared in the Difx MSM, light doesn't know about it and complains that CustomAction:MsiProcessDrivers is an unresolved symbol reference. Is there a way to do this in WiX? No. WiX merges the module's contents via mergemod.dll and doesn't offer the ability to munge incoming rows. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Driver installation linker error
bcs wrote: I am trying to install a driver using Wix 3.0 and DifxAppExtension. When I build my installer I get this linker error: Unresolved reference to symbol 'CustomAction:MsiProcessDrivers' Difx doesn't currently support WiX v3. The Difx extension exists for when they support it. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [WiX-commits] Wix 2 and service
I guess that's arguable. I already had to provide all those details (service name, startup information, etc.) in the EXE itself, in order to support the /install, /remove, /start and /stop switches. Why would I want to repeat that in the installer, instead of just calling the EXE? Thanks and best regards. On Tue, 2007-10-02 at 08:38 -0700, Bob Arnson wrote: Gonzalo Diethelm wrote: The only reason not to use ServiceInstall and ServiceControl is the DRY principle (Don't Repeat Yourself).Since I MUST provide a way for users to start/stop/install/delete the service from the console, I don't want to replicate that mechanism anywhere else, hence the very simple actions in a DLL that invoke these operations. Both DRY and Occam's Razor include the term unnecessarily. Correctly handling service installation isn't simple, so this is a case where repeating the information has value. -- sig://boB http://joyofsetup.com/ -- Gonzalo Diethelm [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Maintenance - Change weirdness
Hi Folks - I've run in to some weirdness with an installation package when trying to modify an existing installation. In Add/Remove Programs, both the Change and Remove buttons are displayed ... but the Change button doesn't work as expected. When the Change button is clicked, the installation package starts ... but it goes straight in to reinstalling the product without giving the user any options to add or remove any features. ARPNOMODIFY is not being set [at least not that I can find] and the installation behaves as expected on the initial install and if the Remove button is clicked ... Thoughts ... ? Have I missed something simple obvious ... ? Thanks in advance, -dmm -- View this message in context: http://www.nabble.com/Maintenance---Change-weirdness-tf4555845.html#a13002172 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Driver installation linker error
I got it working by adding the following Binary Id=DIFxApp.dll SourceFile=$(var.DIFxAppPath)DIFxApp.dll / Binary Id=DIFxAppA.dll SourceFile=$(var.DIFxAppPath)DIFxAppA.dll / CustomAction Id=MsiCleanupOnSuccess BinaryKey=DIFxApp.dll DllEntry=CleanupOnSuccess / CustomAction Id=MsiProcessDrivers BinaryKey=DIFxApp.dll DllEntry=ProcessDriverPackages / CustomAction Id=MsiInstallDrivers BinaryKey=DIFxAppA.dll DllEntry=InstallDriverPackages Execute=deferred Impersonate=no / CustomAction Id=MsiUninstallDrivers BinaryKey=DIFxAppA.dll DllEntry=UninstallDriverPackages Execute=deferred Impersonate=no / CustomAction Id=MsiRollbackInstall BinaryKey=DIFxAppA.dll DllEntry=RollbackInstall Execute=rollback Impersonate=no / InstallExecuteSequence Custom Action=MsiCleanupOnSuccess After=InstallFinalize / Custom Action=MsiProcessDrivers After=InstallFiles / /InstallExecuteSequence Can't remeber where I got this from... Think I extraced it from somewhere... Seems to work for me... You'll also need the set the var DIFxAppPath to point to the DIFxAppA.dll. I think this comes with the windows DDK Garth bcs wrote: I am trying to install a driver using Wix 3.0 and DifxAppExtension. When I build my installer I get this linker error: Unresolved reference to symbol 'CustomAction:MsiProcessDrivers' My Wix source code is shown below. Can anyone help me find out how to avoid this linker error? Thanks Bo ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:difx=http://schemas.microsoft.com/wix/DifxAppExtension; Product Id=c2bf8f6e-ff84-4b27-adc8-4acc9486cfd3 Name=My Driver Language=1033 Version=1.0.0.0 Manufacturer=My Company UpgradeCode=ad6ba1b3-686a-4f49-8c52-84fe1c389d50 Package InstallerVersion=200 Compressed=yes / Property Id=ALLUSERS1/Property Media Id=1 Cabinet=DriverInstallation.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Component Id=ProductComponent Guid=3e0aa007-4463-4f70-aaf2-ad9c1feffb8c difx:Driver AddRemovePrograms=no Legacy=yes PlugAndPlayPrompt=no / File Id=MyDriver.sys Name=MyDriver.sys Source=MyDriver.sys / File Id=MyDriver.inf Name=MyDriver.inf Source=MyDriver.inf / /Component /Directory Feature Id=ProductFeature Title=My Driver Feature Level=1 ComponentRef Id=ProductComponent / /Feature /Product /Wix - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reference one directory up.
Thank you much. I figured it was something simple like that, but I didn't know the syntax for it. On 10/2/07, Chad Petersen [EMAIL PROTECTED] wrote: ..\ is the syntax for one folder up from the current folder. -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Jessi Darling *Sent:* Tuesday, October 02, 2007 8:47 AM *To:* wix-users *Subject:* [WiX-users] Reference one directory up. How do you specify where your files are located when you don't want to hard code the directory, just have it point to one directory up? Thanks in advance. -- Jessica Darling -- Jessica Darling - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Determine which Version of Windows installer isinstalled
Use the VersionMsi standard Windows Installer property. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig0ss Sent: Friday, September 28, 2007 3:41 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Determine which Version of Windows installer isinstalled Hi I need to identify using wix the version of the windows install that is current installed on the sytem, is this done by a reg entry or .dll et etc thank you -- View this message in context: http://www.nabble.com/Determine-which-Version-of-Windows-installer-is-in stalled-tf4533681.html#a12938206 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fw: Some STUPID Limitations in WiX
You should be able to pass transforms generated from wixpdb's in combination with ones generated from admin images. You will need a transform passed to torch for each product you want to target because product code information is important and I assume each language you ship has a different product code. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Tuesday, October 02, 2007 9:07 AM To: Cristian Baiu Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fw: Some STUPID Limitations in WiX Cristian Baiu wrote: So far I don't know how to instruct pyro to address my patch to all MSIs unless I make differences for all of them and pass all these difference sets to pyro. Can you please advice me if it's possible to target multiple MSIs with only one set of differences and how ? You'll need to use Torch's -ax switch to use admin images. I'm not sure how well that works to create one patch that also targets products using .wixpdbs. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fw: Some STUPID Limitations in WiX
I meant pyro when I said torch below. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Marcu Sent: Tuesday, October 02, 2007 10:15 AM To: Bob Arnson; Cristian Baiu Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fw: Some STUPID Limitations in WiX You should be able to pass transforms generated from wixpdb's in combination with ones generated from admin images. You will need a transform passed to torch for each product you want to target because product code information is important and I assume each language you ship has a different product code. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Tuesday, October 02, 2007 9:07 AM To: Cristian Baiu Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fw: Some STUPID Limitations in WiX Cristian Baiu wrote: So far I don't know how to instruct pyro to address my patch to all MSIs unless I make differences for all of them and pass all these difference sets to pyro. Can you please advice me if it's possible to target multiple MSIs with only one set of differences and how ? You'll need to use Torch's -ax switch to use admin images. I'm not sure how well that works to create one patch that also targets products using .wixpdbs. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] DeleteMachineCertificate Failure and code problems
Hi,
I have a uninstall which Fails sometimes but not always
It prints the error
DeleteMachineCertificate: Deleting certificate with friendly name: Garth
DeleteMachineCertificate: Failed to delete certificate with friendly
name: Microsoft Root Authority, continuing anyway.
MSI (s) (94:24) [14:55:59:151]: User policy value 'DisableRollback' is 0
MSI (s) (94:24) [14:55:59:151]: Machine policy value 'DisableRollback' is 0
Action ended 14:55:59: InstallFinalize. Return value 3.
After deleting my certificate successfully.
I don't think it should be trying to delete the MS root Cert!
It doesn't always happen and is not very reproduceable.
It could be due to a classic UNICODE overflow bug in the file
http://wix.cvs.sourceforge.net/wix/wix/src/ca/serverca/scaexec/scacertexec.cpp?view=markup
WCHAR wzFriendlyName[256] = { 0 };
DWORD cbFriendlyName = sizeof(wzFriendlyName);
Should read
WCHAR wzFriendlyName[256] = { 0 };
DWORD cbFriendlyName = countof(wzFriendlyName);
This bug also is in
src/ca/serverca/scasched/scacert.cpp Line 663
src/ca/serverca/scasched/scacert.cpp Line 946
src/ca/serverca/scasched/scacert.cpp Line 1024
Cheers
Garth
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] The folder path '?' contains an invalid character
The only time I've ever seen this error message is when the shell folders registry entries are incorrect. MSI checks every entry in the Directory table for validity, so make sure you don't have a directory/property name that is resolving to a ?, and it's probably worth making sure that these folders are not corrupt: http://windowsxp.mvps.org/usershellfolders.htm Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick Sent: Monday, October 01, 2007 2:57 PM To: 'Matias Woloski'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] The folder path '?' contains an invalid character All I can see in the documentation is this: The SetTargetPath event notifies the installer to check and set the selected path. If the path is not valid to be written to, then the installer blocks further ControlEvents associated with the control. This is a standard part of Windows Installer - there isn't any WiX-supplied code at this point. Perhaps you should ensure that the TARGETDIR property is appropriately initialised before beginning the UI? Having said that, it should be initialised to ROOTDRIVE if not otherwise initialised, and ROOTDRIVE is initialised to the drive with the most free space, so I can't see why this would be a problem. Is this reproducible on a clean system? On Windows XP? (your screenshot looks like Windows Vista with the Classic theme) I think this may be a case for Product Support Services. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matias Woloski Sent: 01 October 2007 22:03 To: wix-users@lists.sourceforge.net Subject: [WiX-users] The folder path '?' contains an invalid character Hi, We're facing an issue with the attached Wix file (SampleWIX.wxs) and Wix 3.0. When the user enters the path *for the first time* where the application will be installed and press Next it shows up an error message: The folder path '?' contains an invalid character (see screenshot). Pressing ok and Next again will work. Do you have any ideas? Thanks Matias - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] dynamically fill a combobox
Collected but not used by me, this VBScript used in a custom action may
help:
Function Combo()
' This function initializes and then sets variables to set values for
the four columns
' of the ComboBox table (Property, Order, Value and Text). Then a
function is called to add
' the row of values to the table.
' Initialize variables used for each column of the ComboBox table
Dim ComboProp
Dim ComboOrder
Dim ComboValue
Dim ComboText
' Set properties for each of the four columns
ComboProp = COMBO
ComboOrder = 1
ComboValue = Dog
ComboText = Dog
' Call function to add this row of values to the ComboBox table
addToComboBox ComboProp, ComboOrder, ComboValue, ComboText
'Repeat Process as needed
ComboProp = COMBO
ComboOrder = 2
ComboValue = Cat
ComboText = Cat
addToComboBox ComboProp, ComboOrder, ComboValue, ComboText
ComboProp = COMBO
ComboOrder = 3
ComboValue = Frog
ComboText = Frog
addToComboBox ComboProp, ComboOrder, ComboValue, ComboText
ComboProp = COMBO
ComboOrder = 4
ComboValue = Bird
ComboText = Bird
addToComboBox ComboProp, ComboOrder, ComboValue, ComboText
End Function
Function addToComboBox(ByVal ComboProp, ByVal ComboOrder, ByVal
ComboValue, ByVal ComboText)
' This function takes values passed into it from the function call and
uses these values to create
' and execute a view within the current session of the Windows Installer
object. This view is based
' on a SQL query constructed using the values passed into the function.
If you wish to get a deeper
' understanding of how this function works you should read up on the
Windows Installer object
' model in the Windows Installer SDK.
' Initialize variables
Dim query
Dim view
' Construct query based on values passed into the function.
' NOTE: The ` character used is not a single quote, but rather a back
quote. This character is typically
' found on the key used for the ~ symbol in the upper left of the
keyboard.
query = INSERT INTO `ComboBox` (`Property`, `Order`,
`Value`, `Text`) VALUES (' ComboProp ', ComboOrder , '
ComboValue ', ' ComboText ') TEMPORARY
' This statement creates the view object based on our query
Set view = Session.Database.OpenView(query)
' This statement executes the view, which actually adds the row into the
ComboBox table.
view.Execute
End Function
=
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, October 02, 2007 1:24 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] dynamically fill a combobox
Hi,
I want to use a custom action to fill dynamically a combobox. But I do
not know how the output of the custom action should look like. I only
think to know that I have to bind a property to the ouput to get the
selected item of the combobox.
Regards, Peter
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fw: Some STUPID Limitations in WiX
The problem you are hitting is that the Wixpdb contains no information about msm's they are merged in after the fact. Three options: 1. Instead of using the wixpdb, just use the admin image functionality I added in order to create transforms for the products that contain msm's. 2. Use Melt.exe to convert your msm into a componentgroup, then remove the msm from your authoring and add in the componentgroup. 3. Don't use MSM's. :) To answer your repair question, it depends on the flags that are passed to msi during the repair, by default the newest version wins. One way to solve the long build time is to consider a langpack model. Where all the files that aren't per language live together in a single msi. This would mean that if you are patching a language neutral component you only have to patch the core msi and not the langpacks. -Original Message- From: Cristian N. Baiu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 02, 2007 11:18 AM To: Peter Marcu; [EMAIL PROTECTED]; Cristian Baiu Cc: wix-users@lists.sourceforge.net Subject: Fw: [WiX-users] Fw: Some STUPID Limitations in WiX Thanks Bob, thanks Peter for your answers. I will not have problems with the localizations. The only problem will be the time to generate a patch, because my setup takes a very long time to build - about 30 mins for each MSI and I have over 20 MSI's (12 languages * 2 - due to x86 and x64). Knowing that my patches (hot-fixes most of them) will patch only non-localizable files (practically will update versioned DLL files), I was hoping I could optimize the patch build process by building only two upgrade MSIs (one for x86 and x64) and then pass by some other means only the product codes for the other MSI's to pyro. I don't know if it would be a best practice but it would sure suite me. Anyway, in lack of alternatives, I will do all the differences. Still, the biggest of my problems is the patching of the MSM which I was talking earlier. I have done some testing, trying to patch a (versioned) dll which is part of my MSM using pyro but had no success. The patch log wasn't saying anything about my file. Then I have tried to build the patch removing all the physical occurences of the file which I needed to patch (the MSM and MSI target and upgrade versions being build at the testing time). I have removed the DLL from my deployment folder - from where the MSM setup resolves it, I have removed the MSM from the folder used by the MSI which includes the MSM, I have removed the upgrade MSI's cabinet from the folder where torch is using it's upgrade wixpdb input file. Then I have build the patch and had no errors. This makes me think that neither torch, candle, light or pyro are even trying to do something with that file. (The reason for all of these was my hope to find out which of them needs to resolve the file and then try to debug it and understand what I've done wrong). Peter, you said in an earlier post that you could provide some workarounds for patching MSMs. It seems I have reached the moment when I need very bad to know them. Could you help me please ? Also Bob said earlier: It will update the shared component but it won't update the other product, so a repair operation can undo the patch. That's why merge modules are falling way out of favor... (refering to a patch for an MSM component which targets only one of more products containing the MSM). These are bad news. I do not know how installer performs the repair so my question is : does the repair replace a newer version of the shared file with an older one if the file is versioned correctly ? Thanks for your answers. I hope I was not too boring with my long story. Cristian. - Original Message - From: Peter Marcu [EMAIL PROTECTED] To: Peter Marcu [EMAIL PROTECTED]; Bob Arnson [EMAIL PROTECTED]; Cristian Baiu [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Sent: Tuesday, October 02, 2007 8:24 PM Subject: RE: [WiX-users] Fw: Some STUPID Limitations in WiX I meant pyro when I said torch below. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Marcu Sent: Tuesday, October 02, 2007 10:15 AM To: Bob Arnson; Cristian Baiu Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fw: Some STUPID Limitations in WiX You should be able to pass transforms generated from wixpdb's in combination with ones generated from admin images. You will need a transform passed to torch for each product you want to target because product code information is important and I assume each language you ship has a different product code. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Tuesday, October 02, 2007 9:07 AM To: Cristian Baiu Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fw: Some STUPID Limitations in WiX Cristian Baiu wrote: So far I don't know how to instruct pyro to address my patch to all MSIs unless I make differences for all of
[WiX-users] Computing space on a password-secured disk causes error
Hello, I have a relatively simple installer. It fails during initialization when it tries to compute the space for a network drive that is password protected. Is there any way to cancel this space-check or only look at local disks? Or, is there a way to continue even if the space check fails? Thanks in advance! -- __ Andre Nelson Software Quality Assurance Manager Frontier Science and Tech Research Foundation - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] The folder path '?' contains an invalid character
On 2 Oct 2007, at 18:54, Wilson, Phil wrote: The only time I've ever seen this error message is when the shell folders registry entries are incorrect. MSI checks every entry in the Directory table for validity, so make sure you don't have a directory/property name that is resolving to a ?, and it's probably worth making sure that these folders are not corrupt: http://windowsxp.mvps.org/usershellfolders.htm I got an error like this (at install time) when I inadvertently had a Directory element with a Name of ... Unsurprisingly that didn't work too well :-) Cheers, Chris - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Release 3.0.3328.0 Assemblies won't bind
Apparently wix.dll was strong named with a different public key this time around while all the other tools are using the correct one. We are looking what caused the problem and will get a fix and release a new build once its fixed. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Lavelle Sent: Tuesday, October 02, 2007 7:24 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Release 3.0.3328.0 Assemblies won't bind Hi, I get the following error when running the Candle.exe in the WiX Release 3.0.3328.0 : Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'wix, Version=3.0.3328.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'wix, Version=3.0.3328.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad' I suspect it's caused by the recent Strong Name changes made by PMarcu, because Release 3.0.3307.0 doesn't give any such problems, and the candle.exe.config in that file has significantly less in it. Or I could be completely wrong... Please advise if you want a bug raised. Regards Martin. _ The information contained in this message, together with any attachments, may be legally privileged or confidential and is intended only for the use of the individual(s) or entity named above. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately before deleting it. This message has been checked for all known viruses through MessageLabs Virus Control Centre, for and on behalf of the AVEVA Group. Although no viruses were found it is the recipient's responsibility to ensure that this message is safe for use on their system. AVEVA Group plc is a Public Limited Company registered in England with registered number 2937296. The registered office of AVEVA Group plc is High Cross, Madingley Road, Cambridge, England CB3 0HB - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [WiX-commits] Wix 2 and service
Why add this functionality to your program when Windows XP and Server 2003 ship net.exe which can start and stop services, and sc.exe, which can create and delete services as well? Net.exe has been able to start and stop services since Windows NT 4.0 at least, and sc.exe was previously part of the Windows Resource Kit Tools. If you want to start and stop services remotely, you can do so with the psservice utility from Sysinternals (http://www.microsoft.com/technet/sysinternals/utilities/psservice.mspx). It's really not necessary to do it in your application. If you're that bothered about repeating yourself, skip the application end. Don't make use of a custom action - very hard to get right - over built-in Windows Installer functionality. -- Mike Dimmick _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gonzalo Diethelm Sent: 02 October 2007 17:24 To: Bob Arnson Cc: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] [WiX-commits] Wix 2 and service I guess that's arguable. I already had to provide all those details (service name, startup information, etc.) in the EXE itself, in order to support the /install, /remove, /start and /stop switches. Why would I want to repeat that in the installer, instead of just calling the EXE? Thanks and best regards. On Tue, 2007-10-02 at 08:38 -0700, Bob Arnson wrote: Gonzalo Diethelm wrote: The only reason not to use ServiceInstall and ServiceControl is the DRY principle (Don't Repeat Yourself).Since I MUST provide a way for users to start/stop/install/delete the service from the console, I don't want to replicate that mechanism anywhere else, hence the very simple actions in a DLL that invoke these operations. Both DRY and Occam's Razor include the term unnecessarily. Correctly handling service installation isn't simple, so this is a case where repeating the information has value. -- sig://boB http://joyofsetup.com/ -- Gonzalo Diethelm [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] website with p3p - repost
2.0.4701 is pretty old now. As far as I can see from the latest release, 5325 (from May this year), this error shouldn't occur. The error would be coming from either validating the XML against the schema - but HttpHeader is listed as an element that can appear under WebSite in the latest schema - or in the compiler as it parses the source - but the presence of HttpHeader is detected and parsed in the method which parses WebSite. I'd suggest trying out this latest version. -- Mike Dimmick _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 02 October 2007 00:11 To: wix-users@lists.sourceforge.net Subject: [WiX-users] website with p3p - repost I'm currently using wix 2.0.4701.0 and writing wxs file for a website that implements Platform for Privacy Performance and for this, I need to add custom header name/ value pair in IIS. It seems like HttpHeader is the proper element for this but got an error: The WebSite element contains an unexpected child element 'HttpHeader'. Please share your idea if someone has done. Thanks, Surya _ Connect to the next generation of MSN Messenger Get it now! http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-ussource= wlmailtagline - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to configure SQL Express bootstrap
Find the Package.xml file for SQL Express, edit it and look for the Command PackageFile=sqlexpr32.exe Arguments=.. element. Change the Arguments to what you want. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Latendresse Sent: Tuesday, October 02, 2007 5:41 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to configure SQL Express bootstrap I created a bootstrapper with MSbuild to install SQL Express, but I'd like to change the configuration... Since it is in a bootstrap it doesn't show the install wizard. Surely configuring the database engine is possible. Does someone have an example or can please point me in the right direction? Thanks. Eric Latendresse Programmer Optimum Solutions, Inc. 615-329-2313x 2229 615-329-4448 fax [EMAIL PROTECTED] www.optimum-solutions.com http://www.optimum-solutions.com/ Your Only Payroll,HR and time attendance solution - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to configure SQL Express bootstrap
Excellent, Thanks! Eric From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 02, 2007 4:57 PM To: Eric Latendresse; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] How to configure SQL Express bootstrap Find the Package.xml file for SQL Express, edit it and look for the Command PackageFile=sqlexpr32.exe Arguments=.. element. Change the Arguments to what you want. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Latendresse Sent: Tuesday, October 02, 2007 5:41 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to configure SQL Express bootstrap I created a bootstrapper with MSbuild to install SQL Express, but I'd like to change the configuration... Since it is in a bootstrap it doesn't show the install wizard. Surely configuring the database engine is possible. Does someone have an example or can please point me in the right direction? Thanks. Eric Latendresse Programmer Optimum Solutions, Inc. 615-329-2313x 2229 615-329-4448 fax [EMAIL PROTECTED] www.optimum-solutions.com http://www.optimum-solutions.com/ Your Only Payroll,HR and time attendance solution - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Light problem in 3.0.3328.0
Since build 3.0.3328's zip file had Strong Name problems, I installed the msi. That package has problems with paths with spaces. Using 8.3 names works ok. It works if you only ask for help, but fails if a link is attempted. Dave c:\Program Files\Windows Installer XML v3\bin\light.exe -? Microsoft (R) Windows Installer Xml Linker version 3.0.3328.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [objectFile ...] -aiallow identical rows, identical rows will be treated as a warning -au(experimental) allow unresolved references, will not create a valid output ---SNIP --- .mst - Windows installer Transform .pcp - Windows installer Patch Creation Package For more information see: http://wix.sourceforge.net c:\Program Files\Windows Installer XML v3\bin\light.exe -out c:\builds\ms08110030\oms\Mstn\bui 'c:\Program' is not recognized as an internal or external command, operable program or batch file. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Silent install won't copy in files
Must be time to create an MSI log of UI and non-UI to see what's going on. Have you searched your system for the files involved? It's not unusual for files to end up being installed at some unexpected location (such as C:\filename), so it's possible that skipping the UI sequence is resulting in an unresolved location that's defaulting to the root drive or something. It's hard to believe they're not installed at all if conditions, install level and so on are all correctly set. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Thursday, September 27, 2007 2:08 PM To: Mike Menaker; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Silent install won't copy in files Indeed. Odd. I've never heard of any issues like this... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Menaker Sent: Wednesday, September 26, 2007 14:09 To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Silent install won't copy in files The problem is that the files aren't copied at all. When doing a normal graphical install they get copied over fine. Silent install they don't get copied at all. I was able to fix this problem by using the directory structure to copy in files instead of CopyFile. It is still odd that CopyFile didn't work. From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 26, 2007 1:49 AM To: Mike Menaker; wix-users@lists.sourceforge.net Subject: RE: Silent install won't copy in files What is the exact problem? I'm a little confused by what you mean when you say it isn't copying 3 files correctly? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Menaker Sent: Friday, September 14, 2007 15:03 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Silent install won't copy in files Hi, I'm having a problem with a silent install. I have a component that copies 2 files and writes to the registry however it isn't copying the 3 files correctly (yet writing the registry correctly). This is my component. Component Id=SpeechConfig DiskId=1 Guid=49861A79-A034-4e15-BA38-783D2FCC4D90 File Id=TEST_cfg Name=TEST_1.CFG LongName=Test.cfg CopyFile Id=CopyTestCfg DestinationProperty=[ProgramFilesFolder]Test\Config\ / /File File Id=USER_XML Name=user.xml LongName=user.xml CopyFile Id=CopyUserXml DestinationProperty=[ProgramFilesFolder]Test\Config\ / /File Registry Id=TEST_SETREG_ADD Root=HKLM Key=SOFTWARE\FLEXlm License Manager\TestLicensingService Name='License' Action='write' Type='string' Value='[ProgramFilesFolder]Test\license_manager\license\test.lic' / /Component Any ideas why it isn't copying in the files correctly? Thanks, Mike - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
