Thanks again Richard,
>> I tried to put the custom action prior to the SpawnDialog like this;
>>
>>
>> > Order="2">1
>> > Order="1">DATAEXPORTDIR_CHECK OR DATALOADERDIR_CHECK
>>
> This isn't right. The Order attribute determines the order in
> which events are processed. This has th
In article <250bf09281efec4398de83072daed6ef713d32c...@ex3.messagegate.local>,
Dale Quigg writes:
> I tried to put the custom action prior to the SpawnDialog like this;
>
>
> 1
> DATAEX
PORTDIR_CHECK OR DATALOADERDIR_CHECK
>
This isn't right. The Order attribute determines
Thanks Bob and Richard.
> Date: Fri, 12 Dec 2008 12:10:40 -0700
> From: Richard
> Subject: Re: [WiX-users] CA called from DoAction
>
>> In article <4941b98f.1040...@joyofsetup.com>,
>>Bob Arnson writes:
>> Dale Quigg wrote:
>>> I have a custom dialog and when I press "Next", I want a custom
This doesn't work. A log will tell you it's unsupported. The feature that the
component is removed from goes into advertised state, and that results in
patches to files in that feature not being applied. See what happens if you
set MSIENFORCEUPGRADECOMPONENTRULES and apply the patch.
Files (b
That can't be all of your code if you are saying that MsiGetProperty is
returning success because you're not checking it in the code. Have you omitted
anything?
Your VBScript custom action might be ion the same place, but are you positive
your C++ is deferred?
Phil Wilson
-Original Mes
In article <1229353482945-1658552.p...@n2.nabble.com>,
md5hans writes:
> We are compiling UNICODE. Using L"CustomActionData" instead of
> _T("CustomActionData") makes no difference.
Its not the source of your problem here, but TCHAR and _T() go
together. WCHAR and L"" go together. You sh
This is'nt strictly WiX related?
Though I have found Jungwook's Custom Action Debugging Tool very useful
for debugging Custom Actions.
http://blogs.msdn.com/astebner/archive/2005/03/07/388739.aspx
I would double check how and where you are setting the CustomActionData
and ensure your actions are
Oh, I think I know what you're saying now. And I believe the answer is you
do need 2 components in order to do so, or so I've read and done.
On Mon, Dec 15, 2008 at 9:10 AM, tgoffice wrote:
>
> Sorry, no this is a missunterstanding (my bad english
> ... :confused:)
>
> How can I differ between
Hi!
We are compiling UNICODE. Using L"CustomActionData" instead of
_T("CustomActionData") makes no difference.
/Hans
Michael Urman wrote:
>
> On Mon, Dec 15, 2008 at 08:32, md5hans wrote:
>> MsiGetProperty (hInstall, L"CustomActionData", szActionData,
>> &dActionDataLen);
>
> The use of L
On Mon, Dec 15, 2008 at 08:32, md5hans wrote:
> MsiGetProperty (hInstall, L"CustomActionData", szActionData,
> &dActionDataLen);
The use of L"CustomActionData" instead of _T("CustomActionData") is
the only thing that jumps out at me. However I would have expected to
see a compilation error if t
Hi!
We are tying to access the "CustomActionData" propert from C++:
#pragma comment(linker, "/EXPORT:modifypackagexml=_modifypackage...@4")
extern "C" UINT __stdcall ModifyPackageXml(MSIHANDLE hInstall)
{
TCHAR szActionData[MAX_PATH] = {0};
DWORD dActionDataLen = MAX_PATH;
MsiGetPr
Sorry, no this is a missunterstanding (my bad english
... :confused:)
How can I differ between a SqlDatabase with and without integrated security,
withoud creating to components with nearly the same content (only the User
differs but I have to duplicate all sql scripts)
cemiles wrote:
>
>
If you remove a component in a minor upgrade/small update (which are the only
recommended ways to use a patch) you will either get a patch build failure or
will orphan that component (it won't get removed and you may lose the ability
to service the entire application if the right sequence of ope
13 matches
Mail list logo
