Programming Guide: Part Availability

# Programming Guide

## Part Availability

In most respects, scriptable parts are developed, built, and packaged like non-scriptable parts. The information discussed in "Building Sample Parts" applies to scriptable and non-scriptable parts. The following items are areas where scriptable parts may require special attention during their development and packaging:

- It is necessary to register all the classes used in a part's interface. It may be necessary to ensure that the IDL for those classes is included in the build process and distribution package. This affects the specifications for the IdlTargets and RgIDL macros defined in the sample makefiles.

- If the part has events and is to be used on Windows 95 or Windows NT to interact with OLE or for use in Visual Basic, it is necessary to ensure that a TYPELIB is built that describes your classes. This is controlled by the ctypelib macro in the sample makefiles. For additional information on the ctypelib utility, see "ctypelib Utility".

- The package produced by the sample build process includes the logic required to register the set of parts and IDL identified in the makefile. This includes any needed invocation of odregprt or scriptrg. For additional information on odregprt, see "odRegPrt Utility". For additional information on scriptrg, see "scriptrg Utility".

[ Top | Previous | Next | Contents | Index | Documentation Homepage ]