.Net Standard lib in the nuget package

[verloka]

Will you add the .Net Standard library into nuget package?

[lissyx]

@carlfm01 is the one expert on .Net, I have no ide what ".Net Standard Library" is, so I'll let him answer :)

[carlfm01]

Hi @verloka, thanks for the interest. As this not on my immediate work path I can't work on this right now, but would be nice to start making it easier to support other frameworks such as .NET Core with a common API, I can review if anyone wants to jump into it.

[dev-bre]

Would be very helpful to have a NetCore compatible version. Any idea of when this would be started?

[lissyx]

@dev-bre As you can see, @carlfm01 is mostly alone on that, so any help here is welcome.

[verloka]

@dev-bre, @carlfm01 - The problem is that DLLImport does not see the deepspeech.so lib in the .Net Standard. DLLImport only correct works on Windows and this is a problem with the .Net Standard.

[lissyx]

he problem is that DLLImport does not see the deepspeech.so lib in the .Net Standard.

Could you please elaborate ? Again I insist, @carlfm01 could use some help from other people that are .Net knowledgeable.

[verloka]

@lissyx dllimport is a built-in Windows feature, so it only works fine on Windows. Other platforms like linux or macos don't. I've ask the .net development team and they said they are working on a new modern feature to import native libraries.
The problem is that the app doesn't provide enough information. Just throws FileNotFound exception.

[lissyx]

@lissyx dllimport is a built-in Windows feature, so it only works fine on Windows. Other platforms like linux or macos don't. I've ask the .net development team and they said they are working on a new modern feature to import native libraries.
The problem is that the app doesn't provide enough information. Just throws FileNotFound exception.

This is still very much unclear here, no context What app are you talking about ? How does DLLImport relates to everything ? Have you traced the system calls ? DLL search path might be wrong ? DLLImport might be lurred because we name the lib libdeepspeech.so and not libdeepspeech.dll ?

[dev-bre]

Just to clarify and avoid adding more confusion to this thread:

DllImport attribute IS supported by NetCore and would work in Linux:
https://docs.microsoft.com/en-us/dotnet/api/system.runtime.interopservices.dllimportattribute?view=netcore-3.1

Not sure why has been stated otherwise, but even the .so extension is not an issue, since the .so imports would work in Linux , the .dll imports would work in Windows. You don't need to specify the extension,you just need to specify the class name.

The not found exception might be that the lib path has not been added to env variable: LD_LIBRARY_PATH

[lissyx]

The not found exception might be that the lib path has not been added to env variable: LD_LIBRARY_PATH

That is only valid on linux, i think the previous comment about that refers to Windows ?

You don't need to specify the extension,you just need to specify the class name

And so what happens on Windows if you name .so ?

[verloka]

And so what happens on Windows if you name .so ?

the name does not matter, i've experimented with different names: .dll, .so, without extension for Windows it works for Linux no