On 23/07/2012 13:20, chasewoofe...@gmail.com wrote:
> You will need to set a PUBLIC parameter before you call the custom action,
> then you set the parameter from within the dll custom action.
You can do this with the MsiSetProperty() function.
Rob
-
On 23/07/2012 13:20, chasewoofe...@gmail.com wrote:
> You will need to set a PUBLIC parameter before you call the custom action,
> then you set the parameter from within the dll custom action.
You can do this with the MsiSetProperty() function.
Rob
-
You will need to set a PUBLIC parameter before you call the custom action, then
you set the parameter from within the dll custom action.
>From my Android phone on T-Mobile. The first nationwide 4G network.
- Reply message -
From: "Natalie Carr"
To:
Subject: [WiX-users] Custom Action /
ne 21, 2012 12:44 PM
Subject: Re: [WiX-users] custom action dll not getting called, debugging advice
thanks everyone for the replies.
i've changed:
to:
and i left my InstallExecuteSequence sequence intact and now the logfile
output from the MSI shows that the MSI is attempting to
toolset.
Subject: Re: [WiX-users] custom action dll not getting called, debugging advice
thanks everyone for the replies.
i've changed:
to:
and i left my InstallExecuteSequence sequence intact and now the logfile output
from the MSI shows that the MSI is attempting to call into m
your log file right before or after you expect your custom action to be
> > called. Another thing to do would be to introduce logging via the MSI
> API's
> > inside your custom action for the beginning and ending points.
> >
> > Jacob
> >
> > -
ing via the MSI API's
> inside your custom action for the beginning and ending points.
>
> Jacob
>
> -Original Message-
> From: Joe Damato [mailto:j...@boundary.com]
> Sent: Tuesday, June 19, 2012 1:13 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [W
inside your custom
action for the beginning and ending points.
Jacob
-Original Message-
From: Joe Damato [mailto:j...@boundary.com]
Sent: Tuesday, June 19, 2012 1:13 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] custom action dll not getting called, debugging adv
hi -
this morning i tried installing my msi without using a full UI and noticed
that the logfile output by the installer shows the dll getting hit.
it seems that InstallExecuteSequence (or the way i am using it) only
happens during non-UI installs. i am currently reading docs about
InstallUISeque
chr...@deploymentengineering.com; General discussion for Windows
Installer XML toolset.
Subject: Re: [WiX-users] Custom action dll that depends on another dll
A.DLL is a C++ dll in binary table.
On Jan 6, 2011, at 18:09, Christopher Painter
wrote:
> I would need more information to be able
A.DLL is a C++ dll in binary table.
On Jan 6, 2011, at 18:09, Christopher Painter
wrote:
> I would need more information to be able to answer that. Do you install the
> DLL's then call them or do you call A.dll out of the Binary table? Is A.DLL
> C++ or C#/DTF?
>
> Christopher Painter, Aut
I would need more information to be able to answer that. Do you install the
DLL's then call them or do you call A.dll out of the Binary table? Is A.DLL
C++ or C#/DTF?
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that des
On 05/01/2011 17:15, Andy Clugston wrote:
> Yes, that was it!
>
I am glad it worked.
note: extern "C" is not needed.
> I guess I have been out of native development too long... Thanks for the
> reminder on the function export.
>
> Thanks again!
>
> On Wed, Jan 5, 2011 at 10:50 AM, Leonidas Spyrop
Yes, that was it!
I guess I have been out of native development too long... Thanks for the
reminder on the function export.
Thanks again!
On Wed, Jan 5, 2011 at 10:50 AM, Leonidas Spyropoulos <
leonidas.spyropou...@formicary.net> wrote:
> On 05/01/2011 15:30, Andy Clugston wrote:
> > Hi Users,
On 05/01/2011 15:30, Andy Clugston wrote:
> Hi Users,
Hey Andy,
>
> I am running into a bit of an issue while attempting to hook a C++ dll
> custom action into my installer. From all my research and debugging it
> appears that I have things setup properly. I have some tracing (message
> boxes) to
R) [mailto:u...@cdc.gov]
Sent: Wednesday, November 24, 2010 3:33 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom Action DLL getting Error 1723
THANK YOU!
I was using a standard C# class library project type (apparently I was blind
to the other WiX project ty
, 2010 8:36 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Custom Action DLL getting Error 1723
Did you create your CA DLL using the WiX DTF CA project types?
-Original Message-
From: Pound, Robert (CDC/OCOO/ITSO) (CTR) [mailto:u...@cdc
Did you create your CA DLL using the WiX DTF CA project types?
-Original Message-
From: Pound, Robert (CDC/OCOO/ITSO) (CTR) [mailto:u...@cdc.gov]
Sent: Tuesday, November 23, 2010 6:03 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom Action DLL
Thanks for the response.
My VS2010 is not creating 2 DLL's (what version are you using? What do I need
to do to get 2 DLL's, if that is what I am supposed to have?). However, I
created another DLL as CATestDLL2.CA.dll in my install folder. Reran install
with same results as before.
Than
Hello, anyone can answer my question? I found that this question has zero views
in the forum.
Thank you.
Best regards,
Shao Voon
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build
Lionel Pinkhard wrote:
I just don't understand why nobody's done it already, am I the only
one who needs ShellExec?
Huh? I did do it already. It's shipping.
--
sig://boB
http://bobs.org
-
Take Surveys. Earn Cash. Influenc
I just don't understand why nobody's done it already, am I the only one who
needs ShellExec?
- Original Message -
From: Bob Arnson
To: Rob Mensching
Cc: Wilson, Phil ; wix-users@lists.sourceforge.net
Sent: Saturday, January 06, 2007 7:06 AM
Subject: Re: [WiX-use
Rob Mensching wrote:
Why don't you guys just look at the authoring and CustomAction code
for this in WiX v3? It should be trivial to port that to WiX v2
syntax and build it yourself... Bob's already done the testing and
would probably save you a lot of trouble.
And there's even a sample
PROTECTED] On Behalf Of Wilson, Phil
Sent: Friday, January 05, 2007 09:52
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom Action DLL
That code doesn't check the value returned by ShellExecute - for all you know
it's returning ERROR_FILE_NOT_FOUND. I'd also put a d
om: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Levi
Wilson
Sent: Friday, January 05, 2007 7:06 AM
To: Lionel Pinkhard; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom Action DLL
Can I see how you have your .wxs file setup to call this?
On 1/5/07, Lionel Pinkha
,
IN ULONG ulReason,
IN LPVOID)
{
switch(ulReason)
{
case DLL_PROCESS_ATTACH:
case DLL_PROCESS_DETACH:
break;
}
return TRUE;
}
- Original Message -
*From:* Levi Wilson <[EMAIL PROTECTED]>
*To:* wix-users@lists.sourceforge.net ; [EMAIL PROTECTED]
*Sent:* Thursday, January
Thanks,
I'll have a look at it, though I'm using WiX 2 at the moment, will be upgrading
once stable.
Lionel
- Original Message -
From: Bob Arnson
To: Lionel Pinkhard
Cc: wix-users@lists.sourceforge.net
Sent: Thursday, January 04, 2007 4:56 PM
Subject: Re:
Lionel Pinkhard wrote:
I'm trying to write a custom action DLL that looks up an MSI variable
and then shellexecutes it, this is turning out to be extremely
difficult, as if I call ShellExecute in Win32 API (using C++), it just
does nothing, everything in the code appears to be working, but it
Anohter thing:
When you are calling the ShellExecute function from .exe file the
program runs in the context of current user.
But
When you are calling the ShellExecute function from the deferred
custom action it can run in the context of Local system accont (if
it is not impersonated). It means t
Yeah, the code would help a lot. That way I would be able to take a closer
look at it to see what you're trying to do here. Did you also check the
returned string from the MsiGetProperty call to ensure that the parameter
that you're passing to ShellExecute is a valid path? You might want to thro
p files that were installed? I mean, without
writing a whole Zip handler?
Regards,
Lionel
- Original Message -
From: Levi Wilson
To: wix-users@lists.sourceforge.net ; [EMAIL PROTECTED]
Sent: Thursday, January 04, 2007 3:28 PM
Subject: Re: [WiX-users] Custom Action DLL
I beli
I believe that if it is a deferred CA you will have limited access to the
MSI database (The "CustomActionData" property only pretty much). Are you
checking the return value from the MsiGetProperty? Maybe post your C++ code
so we can take a look at it, but first of all, can you also throw in a
Me
: WiX ListanSubject: Re:
[WiX-users] Custom Action DLL giving me 1723 ...
None
of the "old" CA's worked from an installation (but work when called from a
'normal' application). I've continued to test and found out that the
'Release'build works but no
my debug-stuff that mess things up.
My
guess is that the 'MSI46.tmp'-file is the DLL, and then it should be +280kb
...
/Jonas
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob
ArnsonSent: den 2 oktober 2006 17:00To: Jonas Jonsson L
(AL/EAB)Cc: WiX L
Jonas Jonsson L (AL/EAB) wrote:
The
DLL (and the new functionality) has of course been tested (on W2K &
W2K3s) outside of an installation, and works just as expected, but when
I try to access ANY functionality in the DLL, I get an Error 1723 and
the installation fails.
Do the other
Ok I got it working now thanks again for your help
--
View this message in context:
http://www.nabble.com/Custom-Action-Dll-problem-tf2042392.html#a5623375
Sent from the wix-users forum at Nabble.com.
-
Take Surveys. Earn
WcaGetProperty() isn't being used anywhere else this is the only call.
What I need to do is combine My license with DX License, but if I leave in
the code for
getting the DXEULA the entire program doesn't even run weird.
I tried with both allocation of memory and tried to see if maybe the fuction
You're probably crashing. The Windows Installer has an exception handler to
ensure that poorly written CustomActions don't hose the transaction.
You should look at other places in the code where WcaGetProperty() is used.
You'll find the WiX code has very, very few hard code buffer sizes.
Instead,
38 matches
Mail list logo
