#Microsoft script debugger for vbscript how to#
Fortunately, an enterprising user worked out how to do this with Microsoft Visual InterDev some years ago, and published it to the InstallShield forums. I began investigating.Īs it turns out, it doesn’t appear that Microsoft provided documentation on how to accomplish this. This is all well and good, but what about for scripters that are more used to stepping through the execution line-by-line in an IDE? This question was posed to me in a training class recently, and I’d always assumed there was some easy way out there should users be curious. LogRecord.StringData( 1) = “HKU CA: ” & Message Set LogRecord = Installer.CreateRecord( 1) ‘ Create a Windows Installer Error Log entry and pass it to the session. Below is a simple function I lifted off of a fellow Flexera consultant for this purpose it relies on the VBScript version of MsiProcessMessage(): The MSI VBScript engine exposes many of the APIs in MSI.dll via the Session object. Regardless of how good your coding skills are, this is a good idea for the consumer of the install to debug why your code might not be performing as expected in a certain scenario. On the Well-Documented side of things is the capability for writing to the MSI log file. The purpose of this post is to delve into the well-documented and also the ill-documented options for getting your VBScript custom actions to work properly. There is a problem though, in that in its Quick and Dirty-ness it can often lead to the process of running an install over and over and over again after tweaking lines of code, hoping that you’ve figured out the issue.
As well, it’s much favored by Enterprise Application Packagers because of its maintainability everybody knows VBScript. OctoRevenera long enjoyed/hated VBScript as a quick and dirty tool for getting a job done.
Debugging VBScript Custom Actions: Fact or Fiction?
0 kommentar(er)
