Creating a Custom Object with WSC - Using the Script Component Wizard
(Page 2 of 4 )
Once you provide the basic details about the component name and version, you’ll need to specify the more technical aspects of your component on the second page of the wizard.
Here you should specify the language you intend to use, add any implementations, and provide the type of error checking you would like to use. Keep in mind that you can change these options later by editing the WSC file, as you’ll soon see. If you’re not sure what to use, just use the ones in the image above.
Specifying a language is pretty straightforward. This will add the necessary <script> element to your WSC file. If you intend to use more than one language, or are undecided, you can always change later, so just pick one. Today’s example is written in VBScript, so that’s what I’ve chosen.
Implementations are used to control your object’s interaction with its host application. If you’re using your object in WSH, you do not need any implementations. The first option adds support for DHTML Behaviors. This allows your script to interact with the browser DOM when creating components for use in web pages or HTML applications. The second option provides support for ASP and will allow you to use ASP-provided objects in your script, such as Response.Write() and Server.MapPath(). Adding one or more of these implementations will not affect your component’s use in scripting. It won’t hurt a thing if they go unused.
Next: Creating the Public Interface >>
More Code Examples Articles
More By Nilpo
