In article <[EMAIL PROTECTED]>,
"Aris Green" <[EMAIL PROTECTED]> writes:
> I have been using managec C++ CA's coded in Visual Studio 2003 for
> installs.
IMO, you might as well just use native C++ at that point.
> Well, you get the picture. One wrinkle, the VC 2005 requires linking to the
I have been using managec C++ CA's coded in Visual Studio 2003 for
installs. You create a .NET dll and use unmanaged exports .e.g
__declspec(dllexport) int __stdcall MyCustomAction(MSIHANDLE hInstall);
All your logic is in the installation package and you don't have to leave a
carcass behind with
MAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Sankaranarayanan
Sent: 30 October 2007 18:36
To: Richard; WiX Users
Subject: Re: [WiX-users] Managed Custom Action using InstallUtilLib.dll
I use custom action for the following operations
1) Read XML Config file and set installer properties
2)
o: WiX Users
Cc: [EMAIL PROTECTED]
Sent: Tuesday, 30 October, 2007 10:03:10 AM
Subject: Re: [WiX-users] Managed Custom Action using InstallUtilLib.dll
In article <[EMAIL PROTECTED]>,
Sankaranarayanan <[EMAIL PROTECTED]> writes:
> I am using Managed Custom Action [...]
What is
In article <[EMAIL PROTECTED]>,
Sankaranarayanan <[EMAIL PROTECTED]> writes:
> I am using Managed Custom Action [...]
What is your custom action doing? The MSDN documentation leads people
to believe that they need managed custom actions for all sorts of
things that the standard actions and
5 matches
Mail list logo
