Anirban Basu wrote:
Are users not
supposed to
use the "INSTALLDIR" variable in their custom actions?
But this is a
windows
installer variable (supposed to set by the windows installer service
itself)
and it should be safe to use it.
MSI doesn't set INSTALLDIR; it's ent
CTED] On Behalf Of Mike
Dimmick
Sent: Tuesday, September 19, 2006 9:18 AM
To: Anirban Basu; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] FW: issue around INSTALLDIR
For your problem you could simply use a to find the
component that contains the assembly. Still, I don't like the
6
15:27To: Mike Dimmick;
[EMAIL PROTECTED]Subject: RE: [WiX-users] FW: issue
around INSTALLDIR
Hi
Mike,
Thanks for the
reply.
I agree that the
approach may not be a good one, but we are not in a position to change
it.
Moreover my
question is not around what is the best practice (I know wh
ether I am right or not?
Thanks for all your
helps and suggestions so far.
Take
Care
Anirban
From: Bob Arnson
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 19, 2006
8:30 PM
To: Anirban
Basu
Cc: Mike Dimmick;
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] FW: is
ck
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 19, 2006
7:18 PM
To: Anirban
Basu; [EMAIL PROTECTED]
Subject: RE: [WiX-users] FW: issue
around INSTALLDIR
Why do you have to register this
assembly? Is BizTalk calling back into this assembly via COM Interop? Is it
simply that you're
Why do you have to register this assembly? Is BizTalk
calling back into this assembly via COM Interop? Is it simply that you're trying
to call the Custom Action implemented in the .NET DLL from _vbscript_? Frankly,
that's messy.
Do it properly: write your custom action as
a 'flat' C++ DLL,
tep not to use
"INSTALLDIR" in custom action?
Take Care
Anirban
-Original Message-
From: Anirban Basu
Sent: Tuesday, September 19, 2006 2:08 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [WiX-users] FW: issue around INSTALLDIR
Hi Rob,
Thanks for your responses so
7 matches
Mail list logo
