SAMPLE: OLE Automation Inproc ObjectLast reviewed: August 5, 1996Article ID: Q107982 |
The information in this article applies to:
SUMMARYAUTODLL demonstrates how to create a OLE automation inproc object.
You can find AUTODLL.EXE (size: 29269 bytes) , a self-extracting file, on these services: On the www.microsoft.com home page, click the Support icon Click Knowledge Base, and select the product Enter kbfile AUTODLL.EXE (size: 29269 bytes) , and click GO! Open the article, and click the button to download the file ftp ftp.microsoft.com Change to the Softlib/Mslfiles folder Get AUTODLL.EXE (size: 29269 bytes) On the Edit menu, click Go To, and then click Other Location Type "mssupport" (without the quotation marks) Double-click the MS Software Library icon Find the appropriate product area Locate and Download AUTODLL.EXE Dial (206) 936-6735 to connect to MSDL Download AUTODLL.EXE (size: 29269 bytes) For additional information about downloading, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q119591 TITLE : How to Obtain Microsoft Support Files from Online Services MORE INFORMATIONAUTODLL implements a OLE automation inproc object (DLL server) called Hello that exposes one property, HelloMessage, and one method, SayHello. It uses an OLE provided IDispatch implementation that is created using CreateStdDispatch. The AUTODLL dynamic-link library (DLL) uses the memory allocator used by the calling task. This is required of all inproc objects. The new and delete operators are redefined to use the calling task s memory allocator and all memory management is done using the redefined new and delete. The interface that AUTODLL exposes is described using an object description language (HELLO.ODL). The mktyplib tool is used to create a type library (HELLO.TLB) from HELLO.ODL. CreateStdDispatch is then used to implement an IDispatch interface using the interface description in the type library. AUTODLL exports DllGetClassObject, which is called by OLE to get the class factory. OLE uses this classfactory to create a Hello object. Automation controllers use the IDispatch interface exposed by the Hello object to access its property and method. AUTODLL also exports DllCanUnloadNow. The SIMPAUTO sample in the Software/Data library demonstrates the implementation of an automation object with the same methods and properties as AUTODLL, but which is an EXE. The main differences between the two samples are in the MAIN.CPP file.
To RunThe Hello object exposes the following:
ProgID : SimpleAutomationInProc.Hello Method & Property Names Notes -------------------------------------------------------------- HelloMessage (prop) Sets and returns string. SayHello (method) Displays HelloMessage in an edit control.Update the path in HELLO.REG to the current location of the object and the type library.
To CompileRequires OLE 2.01 or later. Include device=vmb.386 in the [386Enh] section of SYSTEM.INI. Note that vmb.386 can be found in \OLE2\BIN. Run the WXSERVER.EXE from \OLE2\BIN before running the makefile.
Files
MAIN.CPP Does initialization, redefines new and delete, implements DllGetClassObject, DllCanUnloadNow. and contains code that calls CreateStdDispatch. HELLO.CPP Implements the HELLO object.HELLOCF.CPP Implements the HELLO class factory. HELLO.ODL Object Description Language that describes the property and method that HELLO exposes. HELLO.H Defines the HELLO object and the class factory. TLB.H Header file created by mktyplib. MAKEFILE Makefile for project.VB.MAK, VB.FRM Visual Basic project files to control this sample. |
Additional reference words: 2.00 3.50 4.00 server softlib AUTODLL.EXE
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |