As Michal pointed out, try to use different IDs for <Binary> and <CustomAction>.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Chrzanowski
Sent: Monday, February 04, 2008 6:59 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding a custom action (type 6) in apatchpackage(msp)
Now I tried using torch.exe with .msi files instead of .wixpdb files to
generate a .mst file.
Looking into the .mst file I clearly can see the content of my custom action in
binary form. Using orca I can verify that this transform adds a new row into
the binary table.
When I edit my .wixmst file (using the .wixpdbs) there I find the following
line:
<row op="add" sectionId="/{3C6F7936-A1A9-4F37-A6C2-0DC706900E22}"
sourceLineNumber="c:\program files\wix
v3\wixtest\1.1\WixMondoSample1.1.wxs*12"><field>Binary</field><field>SimpleTest</field></row>
If I interpret this right, this line is telling me, that on row should be added
to the binary table - as I want to. So I guessed that pyro.exe is not applying
the transforms as it is supposed to do. Using the -x option in pyro does not
extract my custom action's binaries, too.
I also tried using the -x option in torch but I got only binaries extracted
when I use .msi files and not .wixpdb files. For the upgraded image I can
extract my custom action vbscript file.
Another possible bug I noticed: If I use pyro with a .mst file I receive the
following error message:
'error PYRO0104 : Not a valid output file; detail: Invalid character in the
given encoding. Line 1, position 1.'
I could not find any information on this error.
Kind regards,
Paul.
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Paul Chrzanowski
Gesendet: Montag, 4. Februar 2008 11:19
An: wix-users@lists.sourceforge.net
Betreff: Re: [WiX-users] Adding a custom action (type 6) in apatchpackage(msp)
Hello, Alexander,
you are right, the '/' was a mistake, but this was only a typo in my mail. We
do not get any error messages from light or candle, etc.
We tested a little bit more and came to the conclusion, that using the pcp file
the custom action type 6 ALWAYS work - even
without editing the pcp binary table with orca(this was a mistake on our side).
But if we try the 'only wix' way using torch and pyro we get the following
error message during installation of our msp package:
DEBUG: Error 2721: Custom action SimpleTest not found in Binary table stream
It seems that the created diff.wixmst or something else is not correct. We used
the same commandline arguments as in the wix help file.
Perhaps you still have an idea. Thank you very much.
Best regards,
Paul.
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Alexander
Shevchuk
Gesendet: Freitag, 1. Februar 2008 18:32
An: wix-users@lists.sourceforge.net
Betreff: Re: [WiX-users] Adding a custom action (type 6) ina patchpackage(msp)
Hello Paul,
I did quick experiment and if I add the "\" in front of the file name, like in
your sample, I get an error message from light.exe (I am using WiX 2.0):
Light.exe : fatal error LGHT0005: The system cannot find the file specified ...
Try:
<Binary Id="SimpleTest" SourceFile="Test.vbs"></Binary>
Instead of:
<Binary Id="SimpleTest" SourceFile="\Test.vbs"></Binary>
Alex
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Chrzanowski
Sent: Thursday, January 31, 2008 11:32 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding a custom action (type 6) in a patchpackage(msp)
Hello, Alexander,
thanks for the fast reply, but unfortunately the binary element is not missing
in our .wxs file.
Here is what our file looks like:
<?xml version="1.0" encoding="UTF-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">
<Product Id="3C6F7936-A1A9-4f37-A6C2-0DC706900E22"
UpgradeCode="28408204-7955-4c76-8AE0-0ADBFB74ADF2"
Name=" Sample Application" Language="1033" Version="1.9.0.0"
Manufacturer="Test Ltd." Codepage="1252">
<Package Id="*" InstallerVersion="200" Compressed="no"/>
<Media Id="1" Cabinet="WixMondoSample.cab" EmbedCab="yes" />
<CustomAction Id="SimpleTest" Return="check" BinaryKey="SimpleTest"
VBScriptCall="Main"/>
<Binary Id="SimpleTest" SourceFile="\Test.vbs"></Binary>
<Directory Id="TARGETDIR" Name="SourceDir" >
<Directory Id="ProgramFilesFolder">
<Directory Id ="INSTALLDIR" Name="TEST">
<Component Id="SampleFile"
Guid="7C9DDA32-66C3-4a0f-AE61-2580B67685C9">
<File Id="f1" Source="...\SampleFile.txt" Name="SampleFile.txt"
DiskId="1"/>
</Component>
</Directory>
</Directory>
</Directory>
<Feature Id="ProductFeature" Title="Main Feature" Level="1">
<ComponentRef Id="SampleFile" />
</Feature>
<UIRef Id="WixUI_Mondo" />
<InstallUISequence>
<Custom Action="SimpleTest" After="AppSearch" />
</InstallUISequence>
</Product>
</Wix>
Kind regards,
Paul.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users