Below is retake on the Include subroutine which heads up the vast majority of my scripts. This incarnation puts a wrapper around Include and is called, for want of a better word, Configure. This subroutine takes no parameters at all. Rather, it builds up a filename based on WScript.ScriptFullName with ".cfg" tagged on, reads it in and then hands it over to ExecuteGlobal. This means that the .cfg file must contain functioning VBScript code.
Provided the .cfg sits side-by-side with the .vbs, the .vbs should work. And if you change locations, change the .cfg code. If the .cfg can't be found, you get an error message. I haven't put in any error trapping yet.
Had fun with "With"/"End With" on this one.
So in the .vbs we haveand in the .cfg we have (for example)
Past (20 years or so) and present code. A variety of languages and platforms. Some gems. More gravel. Some useful stuff and some examples of how not to do it.
Showing posts with label Synthetic Include. Show all posts
Showing posts with label Synthetic Include. Show all posts
Thursday, November 23, 2006
Monday, October 10, 2005
[VBScript] Synthetic Includes in Traditional VBScript Files
Most of us are aware of the entry "Synthetic Includes in Traditional VBScript Files" in the Rube Goldberg Memorial Scripting Page.
Today I stumbled across how to embed test routines in the include file without causing these routines to be activated when the file is included.
My include file is called "StdFunctions.vbs". At the bottom of the file I've put When StdFunctions.vbs is included by a script, ScriptFullName evaluates to the name of that script. It's only when StdFunctions.vbs is run by itself that ScriptFullName ends with "StdFunctions.vbs".
BaseName is one of my routines and look a bit like this: [later that same day]
Read the manual, Bruce, read the manual: why use Basename with .ScriptFullName when you can just use .ScriptName?
Today I stumbled across how to embed test routines in the include file without causing these routines to be activated when the file is included.
My include file is called "StdFunctions.vbs". At the bottom of the file I've put When StdFunctions.vbs is included by a script, ScriptFullName evaluates to the name of that script. It's only when StdFunctions.vbs is run by itself that ScriptFullName ends with "StdFunctions.vbs".
BaseName is one of my routines and look a bit like this: [later that same day]
Read the manual, Bruce, read the manual: why use Basename with .ScriptFullName when you can just use .ScriptName?
Labels:
Synthetic Include,
VBScript
Thursday, August 11, 2005
Synthetic include in VBScript
On the Rube Goldberg Memorial Scripting Page there's a synthetic include for VBScript which I use for everything. Thus the "StdFunctions.vbs" of the previous post.
Labels:
Synthetic Include,
VBScript
Subscribe to:
Posts (Atom)