Our WiX based installer does not build any cabinet. All of the installation
and application files are left uncompressed on the disk image. The WiX file
includes VS 2008 SP1 version of Microsoft_VC90_CRT_x86.msm, which gives error
1309 upon installation. It failed due to the missing file
r elevated via the UAC prompt. It
only works with Impersonate="yes" and the action type is 3073 with
msidbCustomActionTypeNoImpersonate set.
>From: Bob Arnson <[EMAIL PROTECTED]>
>To: Mike Poulson <[EMAIL PROTECTED]>
>CC: WenWu Ru <[EMAIL PROTECTED]>, [EMAIL
A custom action in my installer fails on Vista even if an admin user logs on
and launches the installer. I figured that the custom action needs to have
msidbCustomActionTypeNoImpersonate set and adding Impersonate="no" would fix
the issue. To my suprise, the ActionType is still 1025. Instead,
L PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of WenWu Ru
>Sent: 09 November 2006 15:59
>To: wix-users@lists.sourceforge.net
>Subject: [WiX-users] CreateObject in C++ for .NET COM interop?
>
>Our installer includes a .NET assembly component MyCustomActions.dll, which
>is mar
ns methods
that needs to run application specific business logic, therefore have
dependency on .NET. These methods are invoked via custom actions during
install (after InstallFinalize) or uninstall.
From: "Mike Dimmick" <[EMAIL PROTECTED]>
To: "'WenWu Ru'"
Our installer includes a .NET assembly component MyCustomActions.dll, which
is marked with ¡°.NET COM interop¡± in InstallShield. At installation,
InstallShield runs "regasm MyCustomActions.dll /regfile MyCustomActions.reg
/Codebase" to create registry entries on the target system to allow COM
6 matches
Mail list logo
