/build/static/layout/Breadcrumb_cap_w.png

TARGETDIR

Hello,

I am working on a MSI pkg. There is also a System Folder along with the Application Folder in my solution. Now, the problem I am facing is, TARGETDIR is getting defaulted to C:\ Thus, whole bunch of files gets installed on C:\

I found this suspicious data in log file


Action start 15:09:00: ExecuteAction.
MSI (s) (C4:DC) [15:09:10:425]: Ignoring disallowed property TARGETDIR
MSI (s) (C4:DC) [15:09:10:441]: Ignoring disallowed property USERNAME
MSI (s) (C4:DC) [15:09:10:441]: Ignoring disallowed property SOURCEDIR
MSI (s) (C4:DC) [15:09:10:441]: Ignoring disallowed property ROOTDRIVE
Action 15:09:10: INSTALL.
Action start 15:09:10: INSTALL.


Help needed !!!

0 Comments   [ + ] Show comments

Answers (9)

Posted by: dunnpy 14 years ago
Red Belt
0
Milind,

A quick Google for your issue shows that you may need to use SecureCustomProperties..

Try it and I think you may find your solution.

Thanks,

Dunnpy
Posted by: milindsm 14 years ago
Blue Belt
0
Hey Dunnp,

Thanks!!! It worked!!! But couldn't make out why this was happening..!! Other pkgs that I am working on have the same value but they all are working fine anyway...!!!
Posted by: dunnpy 14 years ago
Red Belt
0
This behaviour is default in Windows Vista (due to UAC) and should only be seen on XP in exceptional circumstances.

Thanks,

Dunnpy
Posted by: milindsm 14 years ago
Blue Belt
0
BTW, Can't I call any of the Msixxx functions while in Elevated mode (During InstallInitialize and InstallFinalize) ???? I am trying to call MsiGetProperty and its failing miserably
Posted by: anonymous_9363 14 years ago
Red Belt
0
Do you mean you're trying to use the Windows Installer APIs? How? And where?
Posted by: milindsm 14 years ago
Blue Belt
0
I am using couple of windows MSI APIs like MsiGetProperty, MsiGetTargetPath etc.in the custom action DLL
Posted by: anonymous_9363 14 years ago
Red Belt
0
I'm wondering why you would want to go through that pain when you could simply pass the properties in the function call...

TBH, your question would best be posed - with code samples and an indication of what the error is and where it occurs - in the relevant MSDN forum.
Posted by: milindsm 14 years ago
Blue Belt
0
I'm wondering why you would want to go through that pain when you could simply pass the properties in the function call...
didn't get you...!!!
Posted by: anonymous_9363 14 years ago
Red Belt
0
Well, like:bReturn = MyFunction([INSTALLDIR], [REBOOT],[WHATEVER_OTHER_PROPERTY])

EDIT:
Actually, a thought just struck me...you're aware that you probably won't be able to access the MSI database in whic your CA runs, as the engine places (what one might call) an exclusive lock on it?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ