Microsoft KB Archive/107982

= AutoDll.exe - OLE Automation Inproc Object =

Article ID: 107982

Article Last Modified on 8/9/2004

-

APPLIES TO

 Microsoft OLE 2.03 Microsoft OLE 4.0, when used with:  Microsoft Windows NT 4.0

 Microsoft Windows NT 3.51 Service Pack 5

 Microsoft Windows 95 </li></ul>

-

<div class="notice_section">

This article was previously published under Q107982

<div class="summary_section">

SUMMARY
AutoDll.exe demonstrates how to create a OLE automation inproc object.

<div class="moreinformation_section">

MORE INFORMATION
The following file is available for download from the Microsoft Download Center:

AutoDll.exe

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

AutoDll.exe 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 Run
The Hello object exposes the following: ProgID : SimpleAutomationInProc.Hello <pre class="fixed_text">  Method and 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 Compile
Requires OLE 2.01 or later.

Include device=vmb.386 in the [386Enh] section of SYSTEM.INI.

NOTE: vmb.386 can be found in \OLE2\BIN. Run the WXSERVER.EXE from \OLE2\BIN before running the makefile. <pre class="fixed_text">  File        Function

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 query words: server

Keywords: kbdownload kbfile kbautomation kbsample KB107982

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.