Using a dynamic linklibrary in vc++

Question

0.00/5 (No votes)

See more:

VC8.0

C++

Hi,

How can i use a dll in VC++ which is created in c#.Please give some idea.

Thanks,
Laje.

Posted 7-Feb-11 0:41am

Satheesh1546

Add a Solution

3 solutions

Solution 3

C++/CLI is a powerful thing; I like the answers based on it.
There is another, little know method based on direct exporting of the method from .NET assembly to unmanaged. Many though it was impossible, but in fact CLI standard allows it. This method makes the solution very smooth, and knowledge of C++ or C++/CLI is not required.

I already gave comprehensive information and references in my old answer:

Please see: loading C# DLL in MFC[^].

—SA

Posted 7-Feb-11 14:34pm

Sergey Alexandrovich Kryukov

Updated 7-Feb-11 14:45pm

v2

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)

Olivier Levrey · Accepted Answer · 2011-02-07T01:53:00

My suggestion is to use a wrapper dll in C++/CLI. The advantage of C++/CLI is you can use both managed and unmanaged (native) code:

- In visual studion create a new project (Project type = Visual C++, CLR. Class Library).
- Name it "wrapper.dll" for example
- Add a reference to your C# dll, so you you can access all its content.
- Then write a few functions in native C/C++ and export them (you might need to rewrite a few structures as well).
- Once you compile wrapper.dll, you can use it from an unmanaged application.

I did this once with Ionic.Zip dll. This is a very easy to use and free library for zipping/unzipping files, and I wanted to use it from native code. I wrote a wrapper and it works nicely :)

Nish Nishant · Accepted Answer · 2011-02-07T03:14:00

Solution 2

Olivier has already answered this with the best possible approach. Here's a free chapter from my book that will possibly help you with taking that approach:

http://www.manning.com/sivakumar/sample-ch04_sivakumar.pdf[^]

Take a look at the section 4.2.1 Accessing a managed library from native code. It covers two approaches, the first one uses CCW, while the second one uses C++/CLI based interop (what Olivier mentioned above).

Posted 7-Feb-11 3:14am

Nish Nishant

Comments

Espen Harlinn 7-Feb-11 14:34pm

Not many can put such weight behind their answers :)

Nish Nishant 7-Feb-11 14:41pm

Thanks Espen :-)

Sergey Alexandrovich Kryukov 7-Feb-11 20:40pm

Hi Epsen, remember my old answer? It can work again here.
--SA

Sergey Alexandrovich Kryukov 7-Feb-11 20:40pm

The approach is good, my 5.
Do you know the very different approach based on direct exporting of .NET assembly method to unmanaged. Please see my alternative answer, referencing my old answer.
--SA

Nish Nishant 8-Feb-11 8:30am

Yeah, I am aware of that (have read a few articles on that technique). I would not recommend it for any non-trivial managed API though.

Sergey Alexandrovich Kryukov 8-Feb-11 18:59pm

This is a matter of discussion. As you can see, I do recommend and think this is practical (also, take into account smoothness of the approach and level of the automation in the first article I reference). Besides, for a good purpose, even a non-trivial API could be nicely "trivialized", I mean given a facade which is highly compatible; I did it successfully.
--SA

Nish Nishant 8-Feb-11 19:03pm

The smoothest solution is to use a C++/CLI wrapper. Your suggestion is basically at the same level as the CCW approach since the caller has to deal with COM types (even if the caller is not a COM client). Also when you need to receive and send back complex structures, it becomes a big hassle.

Sergey Alexandrovich Kryukov 8-Feb-11 19:41pm

Sure, a hassle, I agree, but COM is no better (worse because it contaminated the system registry and generally must die). C++/CLI is powerful. I was against it, but later learned it's now under ECMA standard; and I generally like it (value semantic along is so advanced compared to reference-only C#; also I saw an article (Dr Dobbs?) that proved C++/CLI optimization currently was way more advanced than that in C#.)
--SA