14,734,763 members Sign in

articles quick answers discussions features community help Search for articles, questions, tips

Articles » General Programming » DLLs & Assemblies » Beginners

 

Step by Step: Calling C++ DLLs from VC++ and VB - Part 2

Hans Dietrich Rate me: 4.93/5 (65 votes)
2 Oct 2009 CPOL

This series of articles is a step-by-step guide to constructing C++ DLLs that include C++ functions and C++ classes, and then calling the DLL functions
and classes from VC++ and VB programs.

Download demo project - 37.4 Kb

Introduction
This series of articles discusses four common situations when working with DLLs:

Calling a DLL C++ function from a VC++ application

Part 1
Calling a DLL C++ class from a VC++ application
Part 2 Calling a DLL C++ function from a VB application
Part 3 Calling a DLL C++ class from a VB application
Part 4 Loading a C++ DLL dynamically from a VC++ application

Calling a DLL C++ function from a VB application

In Part 1, I talked about creating C++ DLLs and then using those DLLs in VC++ applications. Sometimes you would like to call a function in a C++ DLL
from a VB application.

Step 1
Here is the code for DLL2, which is taken from Part 1's DLL1:

Hide   Shrink   Copy Code

// DLL2.cpp : Defines the entry point for the DLL application.

//

#include "stdafx.h"
#define DLL2_EXPORTS
#include "DLL2.h"

BOOL APIENTRY DllMain( HANDLE /*hModule*/,

DWORD ul_reason_for_call,
LPVOID /*lpReserved*/
)
 {
switch (ul_reason_for_call)
{
case DLL_PROCESS_ATTACH:
case DLL_THREAD_ATTACH:
case DLL_THREAD_DETACH:
case DLL_PROCESS_DETACH:
break;
}
return TRUE;
}

///////////////////////////////////////////////////////////////////////////////
// GetCycleCount - private function of DLL2.cpp. The static keyword ensures
// that this function name is not visible outside DLL2.cpp.
static inline unsigned __int64 GetCycleCount()
{
unsigned int timehi, timelo;

// Use the assembly instruction rdtsc, which gets the current

// cycle count (since the process started) and puts it in edx:eax.
__asm
{
rdtsc
mov timehi, edx;
mov timelo, eax;
}

return ((unsigned __int64)timehi << 32) + (unsigned __int64)timelo;

}

///////////////////////////////////////////////////////////////////////////////
// Example of an exported function
///////////////////////////////////////////////////////////////////////////////
// GetCpuSpeed - returns CPU speed in MHz; for example, ~2193 will be
// returned for a 2.2 GHz CPU.
DLL2_API int __stdcall GetCpuSpeed()
{
const unsigned __int64 ui64StartCycle = GetCycleCount();
Sleep(1000);
return static_cast<int>((GetCycleCount() - ui64StartCycle) / 1000000);
}</int>

DLL2.h looks like:

Hide   Copy Code

#ifndef DLL2_H
#define DLL2_H

// The following ifdef block is the standard way of creating macros which
// make exporting from a DLL simpler. The DLL2.cpp file is compiled with
// the symbol DLL2_EXPORTS defined at the top of DLL2.cpp. This symbol
// should *not* be defined in any project that uses DLL2. This way any
// other project whose source files include DLL2.h will see DLL2_API defined
// as __declspec(dllimport), whereas within DLL2.cpp, DLL2_API is defined as
// __declspec(dllexport).

#ifdef DLL2_EXPORTS
#define DLL2_API __declspec(dllexport)
#else
#define DLL2_API __declspec(dllimport)
#endif

///////////////////////////////////////////////////////////////////////////////
// This function is exported from the DLL2.dll
DLL2_API int __stdcall GetCpuSpeed();
 #endif //DLL2_H

One difference between the code for DLL2 and the code for DLL1 is that GetCpuSpeed() is declared using __stdcall. This is required for any
C/C++ function that you want to use with VB. Here is what MSDN says about the __stdcall calling convention:

Element Implementation
Argument-passing order Right to left.
Argument-passing convention By value, unless a pointer or reference type is passed.
Stack-maintenance responsibility Called function pops its own arguments from the stack.
An underscore (_) is prefixed to the name. The name is followed by the
at sign (@) followed by the number of bytes (in decimal) in the
Name-decoration convention
argument list. Therefore, the function declared as int
func( int
a, double b ) is decorated as follows: _func@12
Case-translation convention None

Step 2
To test DLL2.dll, I use this VB code:

Hide   Shrink   Copy Code

Private Declare Function GetCpuSpeed Lib "DLL2.dll" () As Integer

Private Declare Sub InitCommonControls Lib "comctl32.dll" ()

Private Sub Form_Initialize()

InitCommonControls
ChDir App.Path

End Sub

Private Sub Command1_Click()

Dim nSpeed As Integer

Dim s As String

Screen.MousePointer = vbHourglass
nSpeed = GetCpuSpeed()
Screen.MousePointer = 0

s = nSpeed

Form1.Text1.Text = "GetCpuSpeed() returned " + s

End Sub

Private Sub Form_Load()

Form1.Text1.Text = ""

End Sub

After copying DLL2.dll to the VB directory, I run VB2.exe and this is what I see:

When I click the button, I get this:

So I know that VB can't find the function GetCpuSpeed() in the DLL. To look at what VB is seeing, I use dumpbin /exports dll2.dll from the
command line:

Hide   Shrink   Copy Code

Microsoft (R) COFF Binary File Dumper Version 6.00.8447

Copyright (C) Microsoft Corp 1992-1998. All rights reserved.

Dump of file dll2.dll

File Type: DLL

Section contains the following exports for DLL2.dll

0 characteristics
403FE342 time date stamp Fri Feb 27 08:21:30 2004
0.00 version
1 ordinal base
1 number of functions
1 number of names

ordinal hint RVA name

1 0 00001010 ?GetCpuSpeed@@YGHXZ

Summary

4000 .data
1000 .rdata
1000 .reloc
4000 .text

This is what you would expect from VC++ - it has "decorated" the name GetCpuSpeed and exports the new mangled name
?GetCpuSpeed@@YGHXZ, which VB doesn't understand. What does this mean? Here is what MSDN says:
The Microsoft C++ compilers encode the names of symbols in C++ programs to include type information in the name. This is called
"name decoration", or "name mangling". The purpose of this is to ensure type-safe linking. The C++ language allows function
overloading where functions with the same name are only distinguished from one another by the data types of the arguments to the
functions. Name decoration enables the linker to distinguish between different versions of overloaded functions because the names of
the functions are encoded or decorated differently.

Step 3

To get back to the problem that VB is having, I need to tell VB that the name associated with export #1 is GetCpuSpeed, not the VC++ decorated
name. There is a simple way to do this: create a DLL2.def file, which looks like this:

Hide   Copy Code

; DLL2.def - defines the exports for DLL2.dll

LIBRARY DLL2
DESCRIPTION 'A C++ dll that can be called from VB'

EXPORTS
GetCpuSpeed

Now I recompile DLL2. To check what change has been made, I run dumpbin again:
 Hide   Shrink   Copy Code

Microsoft (R) COFF Binary File Dumper Version 6.00.8447

Copyright (C) Microsoft Corp 1992-1998. All rights reserved.

Dump of file dll2.dll

File Type: DLL

Section contains the following exports for DLL2.dll

0 characteristics
403F2B8D time date stamp Fri Feb 27 08:35:41 2004
0.00 version
1 ordinal base
1 number of functions
1 number of names

ordinal hint RVA name

1 0 00001010 GetCpuSpeed

Summary

4000 .data
1000 .rdata
1000 .reloc
4000 .text

This shows that export #1 is now named GetCpuSpeed. So I copy the new Dll2.dll file to the VB directory, run the VB app, and click the button. This
is what I get:

Success! I have a VB application calling a function that has been exported from a VC++ DLL. But what about VC++ applications? Can a VC++
application call the same DLL as a VB application?

Step 4
I copy the EXE code from Part 1, remove the code that tests the C++ class, compile it, and run it. Here is what I get when I press the button:

So I have one DLL that can be called by a VC++ application and a VB application. This was accomplished by use of a module definition (.DEF) file.

Step 5

Since the DLL now has a .DEF file, there is no need for the __declspec(dllexport) and __declspec(dllimport). I change DLL2.h to:

Hide   Copy Code

 #ifndef DLL2_H
#define DLL2_H

///////////////////////////////////////////////////////////////////////////////
// This function is exported from the DLL2.dll
int __stdcall GetCpuSpeed();

#endif //DLL2_H

and also update DLL2.cpp.

Key Concepts

To avoid name-mangling problems and having to Alias function names in VB, use module definition (.DEF) files.
When using .DEF files, it is not necessary to use __declspec(dllexport) or __declspec(dllimport).
Use __stdcall for functions that are called by VB.
DLLs implemented with .DEF files can be called by both VC++ and VB programs (without needing to use Alias).

Demos

The EXE2.exe and VB2.exe demos test the GetCpuSpeed() function in DLL2.dll:

Revision History

Version 1.1 - 2009 October 3

Added string example to Part 2.

Version 1.0 - 2004 February 29

Initial public release

Usage
This software is released into the public domain. You are free to use it in any way you like, except that you may not sell this source code. If you modify
it or extend it, please to consider posting new code here for everyone to share. This software is provided "as is" with no expressed or implied warranty.
I accept no liability for any damage or loss of business that this software may cause.
License
This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Hans Dietrich
Software Developer (Senior) Hans Dietrich Software
United States

I attended St. Michael's College of the University of Toronto, with the intention of becoming a priest. A friend in the University's Computer Science
Department got me interested in programming, and I have been hooked ever since.

Recently, I have moved to Los Angeles where I am doing consulting and development work.

For consulting and custom software development, please see www.h...

show more

Comments and Discussions

 

You must Sign In to use this message board.

Search Comments

Spacing Relaxed   Layout Normal   Per page 25     Update

First Prev Next

No Entry Point Member 10030341 5-May-13 11:55 

Callin VB DLLs from VC++ (visual studio 2010) Member 9194833 16-Jul-12 1:07 

Awesome, was super helpful ! Dan Clark 1-Apr-11 16:20 

pass a bitmap from vb.net to c++ dll frito_burrito 15-Mar-10 11:28 

Create DLL in C and call from VB karthickbabu_india 2-Nov-07 1:05 

how can define function in .def file mvnevis 5-Jul-07 2:31 

Calling a C Builder DLL from a VB App Luiscperu 19-Feb-07 6:04 

Anybody interested in VC++ Directory Utility ? avanish123 1-Feb-07 6:48 

 Calling C++ DLLs from Matlab maritkap 5-Dec-06 23:34 

creating a DLL which holds info (array and parameters) for shabya 21-Apr-06 2:35 
applications

some Extention dll questions? roseblood 19-Apr-06 21:02 

c++ globals behaviour jsep 18-Feb-06 21:24 

Kudos K. Shaffer 10-Jan-06 6:23 

LNK 4003 Allwyn D'souza 19-Sep-05 8:53 

Problem with calling a C++ DLL from VB gjcsot 5-Sep-05 9:19 

Re: Problem with calling a C++ DLL from VB MANISH RASTOGI 26-Jun-08 3:03 

debugging c from vb deodiaus 10-May-05 15:59 

Re: debugging c from vb Anonymous 3-Jun-05 6:58 

Re: debugging c from vb Cristian Amarie 6-Jan-07 1:58 

Using COMObject from Matlab to C# Anonymous 30-Apr-05 12:06 

Re: Using COMObject from Matlab to C# Member 1976471 19-May-05 3:08 

Both VB and C++ Friendly DLL jcapzz 6-Apr-05 6:13 

Very Helpful but can you help me further? kezhu 23-Mar-05 1:54 

No help whatsoever robertbiro 30-May-04 18:01 

return string from C++ DLL Member 536415 13-Apr-04 20:23 

Last Visit: 18-Jan-21 3:55     Last Update: 18-Jan-21 3:55 Refresh 1 2 Next ᐅ

General    News    Suggestion    Question    Bug    Answer    Joke    Praise    Rant    Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink Layout: fixed | fluid Article Copyright 2004 by Hans Dietrich

Advertise Everything else Copyright © CodeProject, 1999-2021
Privacy
Cookies Web06 2.8.20210116.1
Terms of Use