Actually, pubca.wixlib isn't really a config file. It is comparable to a .lib
file for C/C++, and the pcashed.dll and pcaexec.dll are only companion files of
pubca.wixlib.
Fredrik
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jdrake
Sent: Friday, Jun
Correct, the dll files are relative to the wixlib in 2.0. In WiX 3.0, there
is a single binary for extensions so this problem no longer occurs. It's a
pain in 2.0 :)
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of jdrake
Sent: Friday, June 23, 200
This may be a poor assumption on my part... but I assumed that the dlls
needed to be relative to the light executable. Instead it appears that they
need to be relative to the pubca.wixlib file.
My base assumption is that config files point to things, and it is a safe
assumption that they are rel
Title: Re: [WiX-users] FW: COM+ custom actions
It’s supposed to be case-insensitive
because you are specifying a class name directly. In WiX 3.0 you can merely
specify the assembly name of the extension (which is case-insensitive). Please
do not open a bug on this issue since its by-desig
Thanks! That answered my question
PERFECTLY!
It all works now.
__
Don Tasanasanta
VIACK Corporation
425-605-7423
From: Rob Mensching
[mailto:[EMAIL PROTECTED]
Sent: Friday, June 23, 2006 12:58
PM
To: Don Tasanasanta;
wix-users@lists.source
Title: Re: [WiX-users] FW: COM+ custom actions
This seems to be a know issue, as per
http://sourceforge.net/tracker/index.php?func=detail&aid=1245159&group_id=105970&atid=642714 .
As for candle begin case sensitive, you are invited t open a bug: [http://sourceforge.net/tracker/?group_id=105970
So not only is Votive-2.0.4103.0.msi missing the pcaext.dll; the command line
to candle is case sensitive, which strikes me as odd, since Windows is not.
Any word on when the extension will be integrated with Votive?
Thanks,
Joshua
--
View this message in context:
http://www.nabble.com/RE%3A-CO
Now light is complaining about File of Type 'Binary' with name 'pcaexec.dll'
could not be found. and the same for pcasched.dll.
Both of these are in the Bin and root directory for the Windows Installer
XML.
Any ideas?
Thanks again,
Joshua
--
View this message in context:
http://www.nabble.com
Read about the ALLUSERS
Property.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta
Sent: Friday, June 23, 2006 11:59
AM
To:
wix-users@lists.sourceforge.net
Subject: [WiX-users] using HKMU
registry attribute
From what I’ve read the Root=”HKMU”
From what I’ve read the Root=”HKMU” value makes
it so the registry entry will appear in HKLM when a per-machine install is run
and in HKCU when a per-user install us run. Is this correct?
In my tests so far my registry entry is always showing up in
HKCU and not switching over t
(Forgot to hit "Reply All"...)
You may want to check that you are doing this:
- Calling candle like this: candle.exe *.wxs -ext
Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext
- Declaring the pca namespace like this: http://schemas.microsoft.com/wix/2005/02/pubca";>
Frederik
>
> >
I have done so now, and I am getting the error:
Could not find extension
'Microsoft.Tools.WindowsInstallerXML.PcaCompiler,pcaext'.
>From the looks of it the Votive install did not even place the pcaext dll in
the Bin directory.
I am not sure, however, all the dlls that are required to support
Did you specify the necessary -ext option on the command line for candle to
use the extension?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of jdrake
Sent: Friday, June 23, 2006 10:46 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] COM+ cus
I am getting the error The Component element contains an unexpected child
element 'pca:ComPlusApplication'.
--
View this message in context:
http://www.nabble.com/RE%3A-COM%2B-custom-actions-t1579119.html#a5016225
Sent from the wix-users forum at Nabble.com.
Using Tomcat but need to do more? Ne
Just wanted to add that there is a section for job postings on the
InstallSite.org forum:
http://forum.installsite.net/index.php?showforum=65
--
Stefan Krueger
Microsoft Windows Installer MVP
Please post your questions in the newsgroup or vist one of these web sites:
Windows Installer FAQ
htt
The error is E_ADS_BAD_PATHNAME: An
invalid directory pathname was passed
Seems likely that the website path
provided on the commandline was invalid.
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jon Hardenbrook
Sent: Friday, June 23, 2006 5:14
AM
Peter G. Sakhno wrote:
> Hello.
>
> I need to run external stand-alone exe-file that is not part of the
> installation package and is not included into Binary table.
> Does anybody can explain how to create such custom action using WiX?
>
> I tried following:
>
> ExeCommand="[SourceDir][ExeFilePA
Albert van Peppen wrote:
This way there is no need to build a
seperate wixlib and you can keep everything in one project easily.
True, though you're recompiling more every time than if you built a new
.wixlib.
It would be neat if you could 'override' a
specific dialog. Then you
Since the Archive is down on the website I don’t know
if there is a history on this or not. I followed the directions to harvest a
website and received:
heat.exe : error HEAT0001 : Unknown error (0x80005000)
Exception Type: System.Runtime.InteropServices.COMException
Stack Trac
Hello.
I need to run external stand-alone exe-file that is not part of the
installation package and is not included into Binary table.
Does anybody can explain how to create such custom action using WiX?
I tried following:
and get an error during installation. Log says:
Doing action: EXEFI
Sorry about that post - it got thoroughly MIMEd - I won't try that again!
Ian Thomas
GeoSciSoft - Perth, Australia
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Applica
Hmm.. I did it some other way; maybe the wrong way? But
it is much easier (at least it seems to me and it works);
1. Copy the WixUI_.wxs (for example the
WixUI_Mondo.wxs) to your projects include folder (yes, i really using them) as
WixUI_MyCustom.wxi
2. Edit the WixUI_MyCustom.wxi: Change
22 matches
Mail list logo
