Need help Implementing third party .net dll interface labview 2018

[PincoG]

Hi Guys,

I have near no experience in implementing C# Dll.

I have only done once for a master IOLink but was very flat and easy.

This time this class is full of Interfaces and I don't have even a clue for where to start.

May you give me some advice?

Thankyou

[wiebe@CARYA]

That doesn't look like a .net dll to me.

Based on the headers it's a PE dll, so you should be using CLFNs to interface with it.

PE dlls are quite different from .net dlls. They're a hole lot harder to grasp and will crash LV (a lot) if you're not doing it right.

You can try the Tools>Import>Shared library... wizard. But I wouldn't get my hopes up.

[wiebe@CARYA]

I gave your post it's own thread, as it's not directly related to the thread you posted in.

[PincoG]

Sorry wiebe@CARYA,

the firm who did this, told me this assemlby was written in C# and based on .Netframework 4.8.1  

How can I verify this assumption?

Greetings

[PincoG]

Sorry guys,

I think I'm doing a little bit of confusion: I have to version of the same library, or at least for the same purpose.

Here attached the C# version.

[wiebe@CARYA]

---

@PincoG wrote:

Sorry wiebe@CARYA,

the firm who did this, told me this assemlby was written in C# and based on .Netframework 4.8.1  

How can I verify this assumption?

Greetings

---

Guess you found a way already.

If you try to open the dll with as a .net assembly, you'll get an error if it isn't a .net dll.

If you try to open the dll with as CLFN, you won\t see any exported functions if it isn't a PE dll.

The reverse isn't true, if you do get an error or see any exported functions, a lot could be wrong (wrong bitness, name mangling, missing dependencies).

[wiebe@CARYA]

That's indeed a framework 4.8 .net assembly.

So what's the question?

To get (you) started we'd need to know what you're trying to do and optionally where you get stuck.