Re: [WiX-users] Adding a custom action (type 6)in a patchpackage(msp)
@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/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding a custom action (type 6)in a patchpackage(msp)
I already tried and retried it, but with no success.
Under the following address I uploaded a .zip file containing my .wxs
files and make batch files.
http://rapidshare.com/files/89307445/WixTest.zip.html
http://rapidshare.com/files/89307445/WixTest.zip.html
It would be nice if anybody would try it out and post her/his result.
Make sure to adjust the paths in the batch files (especially in the
torch.exe command line and the -x option!!).
The first batch file uses .wixpdb files for torching and creates a
.wixmst file. Creating the patch with pyro succeeds but the custom
action binary stream is not added in the binary table.
The second batch file uses .msi files for torching and creates a .mst
file. Creating the patch with pyro fails?! There seems to be an encoding
error and I cannot get this running.
But if you use orca and 'apply' the .mst file on the WixSample.msi you
will see that the binary stream for the custom action is added.
Help is as always much appreciated.
If you already received a similar email, then please excuse me I tried
attaching the zip file directly with my post.
Kind regards,
Paul.
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von
Alexander Shevchuk
Gesendet: Montag, 4. Februar 2008 19:03
An: wix-users@lists.sourceforge.net
Betreff: Re: [WiX-users] Adding a custom action (type 6)in
apatchpackage(msp)
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*12fieldBinary/fieldfieldSim
pleTest/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
Re: [WiX-users] Adding a custom action (type 6) in a patchpackage(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/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding a custom action (type 6) in a 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/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Adding a custom action (type 6) in a patchpackage (msp)
Hello, wix users, we are considering to switch from using InstallShield software to WiX. We want to add and use a new custom action (type 6) integrated in our new hotfix. Sadly, this is not possible with InstallShield's AdminStudio (QuickPatch). Now, we were investigating if WiX would come along with a solution, but we could not manage to achieve this, either. First we used Wix v3 and tried to build a patch using only WiX (torch.exe, pyro.exe) like the tutorial in the help file document. After some experimenting, we got the error indicating that the custom action was not found in the binary table. Only in-line script custom actions (custom action type 38) seemed to work. Then we tried the ordinary way with a pcp file ... leading to the same result. BUT after editing the pcp file with Orca and manually inserting a new entry for the custom action in the binary table the resulting msp file worked just fine! So our question is, is this possible without manual intervention using orca or do we even do anything wrong? Or is this some kind of a bug in creating the msp or wixmst or something like that? Any thoughts regarding our problem are much appreciated. With best regards, Paul. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] Adding a custom action (type 6) in a patchpackage (msp)
Paul, Sounds like your WiX code is missing the Binary element. Basically, the idea is: - Create a record in the CustomAction table: CustomAction Id=MyAction BinaryKey=ExtScript VBScriptCall=SomeFunction / - Create a record in the Binary table: Binary Id=ExtScript SourceFile=ExtScript.vbs/ - Schedule a custom action: InstallExecuteSequence Custom Action=MyAction ... / /InstallExecuteSequence Alex From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Chrzanowski Sent: Thursday, January 31, 2008 6:42 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Adding a custom action (type 6) in a patchpackage (msp) Hello, wix users, we are considering to switch from using InstallShield software to WiX. We want to add and use a new custom action (type 6) integrated in our new hotfix. Sadly, this is not possible with InstallShield's AdminStudio (QuickPatch). Now, we were investigating if WiX would come along with a solution, but we could not manage to achieve this, either. First we used Wix v3 and tried to build a patch using only WiX (torch.exe, pyro.exe) like the tutorial in the help file document. After some experimenting, we got the error indicating that the custom action was not found in the binary table. Only in-line script custom actions (custom action type 38) seemed to work. Then we tried the ordinary way with a pcp file ... leading to the same result. BUT after editing the pcp file with Orca and manually inserting a new entry for the custom action in the binary table the resulting msp file worked just fine! So our question is, is this possible without manual intervention using orca or do we even do anything wrong? Or is this some kind of a bug in creating the msp or wixmst or something like that? Any thoughts regarding our problem are much appreciated. With best regards, Paul. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] 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/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
