Custom action writes entire vbscript into log file.
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?
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
Answers (3)
Please log in to answer
Posted by:
Cosmin Pirvu
12 years ago
This is the normal Windows Installer behavior. If you want to avoid it, a solution is to use a DLL or EXE custom action.
Posted by:
piyushnasa
12 years ago
HAve you tried VBScript from installation option. it will store the VBScript in Binary and will not display in log file.
Posted by:
vaibhavi
12 years ago
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
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