In MSI Installer I have a VB script custom Action
If I make it as a "Deferred Execution in System Context" then entire VB script is being written into log files during InstallFinalize.
Log file has following detail.
Executing op: CustomActionSchedule(Action=ReplaceXXX,ActionType=7206,Source='Copying files
Dim somevariables
Set oFSO = CreateObject("Scripting.FileSystemObject")
set shell = CreateObject("WScript.Shell")

'now it displays vbscript code which is there in custom action.....

MSI (s) (30:60) [11:15:22:143]: Creating MSIHANDLE (148) of type 790536 for thread 10336

does anybody know how to avoid it?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2
This is the normal Windows Installer behavior. If you want to avoid it, a solution is to use a DLL or EXE custom action.
Answered 03/28/2012 by: Cosmin Pirvu
Senior Yellow Belt

Please log in to comment

Answers

0
HAve you tried VBScript from installation option. it will store the VBScript in Binary and will not display in log file.
Answered 03/29/2012 by: piyushnasa
Red Belt

Please log in to comment
0
I tried "VB Script in Binary Table", but it did not solve the problem.
I am not able to add "VB Script installed with this product", as during upgrade it does not find vbscript and it fails.

Let me try creating dll
Answered 03/30/2012 by: vaibhavi
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity