Click here to Skip to main content
15,886,137 members
Articles / Programming Languages / C++

Understanding Custom Marshaling Part 1

Rate me:
Please Sign up or sign in to vote.
4.97/5 (53 votes)
18 Aug 2006CPOL31 min read 206.9K   1.4K   147  
Learn the fundamental principles of COM custom marshaling by code examples.
========================================================================
    ACTIVE TEMPLATE LIBRARY : BasicSample01Interfaces Project Overview
========================================================================

AppWizard has created this BasicSample01Interfaces project for you to use as the starting point for
writing your Dynamic Link Library (DLL).

This file contains a summary of what you will find in each of the files that
make up your project.

BasicSample01Interfaces.vcproj
    This is the main project file for VC++ projects generated using an Application Wizard. 
    It contains information about the version of Visual C++ that generated the file, and 
    information about the platforms, configurations, and project features selected with the
    Application Wizard.

BasicSample01Interfaces.idl
    This file contains the IDL definitions of the type library, the interfaces
    and co-classes defined in your project.
    This file will be processed by the MIDL compiler to generate:
        C++ interface definitions and GUID declarations (BasicSample01Interfaces.h)
        GUID definitions                                (BasicSample01Interfaces_i.c)
        A type library                                  (BasicSample01Interfaces.tlb)
        Marshaling code                                 (BasicSample01Interfaces_p.c and dlldata.c)

BasicSample01Interfaces.h
    This file contains the C++ interface definitions and GUID declarations of the
    items defined in BasicSample01Interfaces.idl. It will be regenerated by MIDL during compilation.
BasicSample01Interfaces.cpp
    This file contains the object map and the implementation of your DLL's exports.
BasicSample01Interfaces.rc
    This is a listing of all of the Microsoft Windows resources that the
    program uses.

BasicSample01Interfaces.def
    This module-definition file provides the linker with information about the exports
    required by your DLL. It contains exports for:
        DllGetClassObject  
        DllCanUnloadNow    
        GetProxyDllInfo    
        DllRegisterServer	
        DllUnregisterServer

/////////////////////////////////////////////////////////////////////////////
Other standard files:

StdAfx.h, StdAfx.cpp
    These files are used to build a precompiled header (PCH) file
    named BasicSample01Interfaces.pch and a precompiled types file named StdAfx.obj.

Resource.h
    This is the standard header file that defines resource IDs.

/////////////////////////////////////////////////////////////////////////////
Proxy/stub DLL project and module definition file:

BasicSample01Interfacesps.vcproj
    This file is the project file for building a proxy/stub DLL if necessary.
	The IDL file in the main project must contain at least one interface and you must 
	first compile the IDL file before building the proxy/stub DLL.	This process generates
	dlldata.c, BasicSample01Interfaces_i.c and BasicSample01Interfaces_p.c which are required
	to build the proxy/stub DLL.

BasicSample01Interfacesps.def
    This module definition file provides the linker with information about the exports
    required by the proxy/stub.
/////////////////////////////////////////////////////////////////////////////

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Systems Engineer NEC
Singapore Singapore
Lim Bio Liong is a Specialist at a leading Software House in Singapore.

Bio has been in software development for over 10 years. He specialises in C/C++ programming and Windows software development.

Bio has also done device-driver development and enjoys low-level programming. Bio has recently picked up C# programming and has been researching in this area.

Comments and Discussions