5 replies to this topic

[AntonS]

Hello!

How I can call development environment from custom action VBScript code?

Article below explain a propblem with STOP statement.

http://support.micro...kb;en-us;252895

Neither fixed JITDebug key in registry, or not I can't call debugger with STOP statement.

[Stefan Krueger]

Have you tried "Debugging Custom Actions" at http://www.installsi...s/en/msi/ca.htm

[AntonS]

Second sentence of article "Debugging Custom Actions", provided with WMI SDK state, that the techniques described in this section only for DLL CA.
It is not possible to use dynamic debugging with custom actions based on Executable Files or Scripts (like Custom Action type 6).

How is it actually?

"Debugging Custom Actions" from www.installsite.org explain additionally MsiBreak environment variable and Debugging Support in IPWI 2.x.

I suppose both of additional methods mean attach to process with Visual Studio C++.

Therefore, Script Custom Actions (like type 6) impossible to debug at runtime?

[Stefan Krueger]

I believe this is one of the disadvantages of VBScript custom actions - you can't really debug them. Use MsgBox and logging instead

[Zweitze]

Try using the Microsoft Script Debugger, and show a messagebox in the CA. MSD is the same debugger you use to debug ASPs.

Note that whether MSD can debug Windows Installer scripts depends on the way Windows Installer runs scripts. (I have no experience with this, just know how to extend software with Active Scripting...)

[AntonS]

But Microsoft Script Debugger can't be attached to MSIEXEC process?
Thereby I can debug with MSD script, used in CA only, separately from installation process.