You are not logged in.

Thread: Calling a .NET library (.dll) from a Qt application

Dear visitor, welcome to QtForum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

magpielover

Beginner

  • "magpielover" is male
  • "magpielover" started this thread

Posts: 13

Location: Finland

  • Send private message

1

Wednesday, January 11th 2012, 3:23pm

Thread: Calling a .NET library (.dll) from a Qt application

Hello,
I am conducting a research about text clustering and have found a third party library written in .NET. However, I haven't used .NET and am not familiar with VS .NET environments. I would like to use the library I found in my pure c++ application. I googled and found some possible ways to do that. For example ActiveQt
To be honest, I didn't find it useful for my purpose because it only demonstrates how Qt objects can be used in a .NET environment not how .NET objects can be used in a Qt environment.

I have a few questions.

Should I modify the source code of the library I found such as making it a COM object?
If so, how?
I guess it's possible to call the library as a COM object from Qt. But I am not sure how to do that.

Second question is, is there anyone who had a similar problem and have managed to solve it or is there any descriptive tutorial I can follow?

The question is pretty simple, I need to call a third party .NET dll in Qt.

Hope you can help me.

Thanks

Amleto

Professional

Posts: 1,430

  • Send private message

2

Wednesday, January 11th 2012, 5:18pm

The question is pretty simple, you need to call a third party .NET dll in c++

http://support.microsoft.com/kb/828736 and plenty more from google
If you have a problem, CUT and PASTE your code. Do not retype or simplify it. Give a COMPLETE and COMPILABLE example of your problem. Otherwise we are all guessing the problem from a fabrication where relevant details are often missing.

Similar threads

Used tags

.NET dll