Creating C++ wrapper for WPF

Question

2.00/5 (1 vote)

See more:

i have one dll Apms.dll which is not supported to WPF (.net).

So i need to write a wrapper in C++ and use it in WPF appln.

iam new to wrapper creation . i have some API calls for Apms.dll .They are

RETCOND API1090 ApmsApiSrvConnect
( LPTSTR szServerName, LPDWORD dwClientNbr,
LPDWORD dwReserved );

Return code is of

R_NORMAL

R_NOCONN

R_NOACTIVE ..

can anybody help me in writing this Wrapper for the Api method in C++ and connect with my WPF application?

Posted 17-Apr-13 2:24am

Member 8786335

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Richard MacCutchan · Answer 1 · 2013-04-17T03:05:00

Solution 1

You need to look into the use of P/Invoke[^] for accessing C style DLL functions from .NET applications.

Posted 17-Apr-13 3:05am

Richard MacCutchan

Comments

Espen Harlinn 17-Apr-13 10:40am

Right, or use C++/Cli :-D

Philippe Mori · Answer 2 · 2013-04-17T17:13:00

Using a mixed mode C++/CLI DLL might be an easy way to provide a .NET friendlier interface for calling code in APms.dll. However if you only have a few functions to call, then the P/Invoke approach would be a better choice.

Typically, if P/Invoke is sufficient then you should go with it. On the other hand, if the DLL is relatively complex to use, wrapper might also help to simplify the use of its function.

I guess that Apms.dll is external to your company and that you only have the DLL (and its library for linking).

Because, if you have the full source code, you might consider compiling the DLL in mixed mode and have the .NET wrapper in the same DLL,