--Original Message-
From: md5hans [mailto:hans.olaus...@carmenta.com]
Sent: Monday, December 15, 2008 6:32 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Reading CustomActionData property from C++
Hi!
We are tying to access the "CustomActionData" propert from C++:
#p
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
Sent: 15 December 2008 15:05
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Reading CustomActionData property from C++
Hi!
We are compiling UNICODE. Using L"CustomActionData" instead of
_T("CustomActionData") makes no difference.
/Hans
Michael Urman wrote:
&
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
6 matches
Mail list logo
