3 ms·
AFAIK, the IJW bits of the CLR are exclusive to Windows.
by zamalek 2y ago
AFAIK, the IJW bits of the CLR are exclusive to Windows.
- neonsunset 2y agoAnd strongly in a "do not use unless you must" category too.
- pjmlp 2y agoStill easier than dealing with P/Invoke or COM interop for C++ libraries, for C++ skilled devs. Pity that never made the cross platform jump.
- neonsunset 2y agoGive this tool a try: https://github.com/dotnet/ClangSharp?tab=readme-ov-file#generating-bindings https://github.com/dotnet/ClangSharp?tab=readme-ov-file#gene... Just specify the headers to generate bindings for, and then use the generated interop code. Not too different from importing them as it was in the past.
- pjmlp 2y agoThanks for the tip.
- pjmlp 2y agoWhat is exclusive is the Visual C++ backend, because of the usual politics, C++ stuff is not under .NET team. Likewise the whole WinRT/UWP, .NET Native and C++/CX, were under WinDev umbrella, not DevDiv. Which is why there is this schizophrenic way of how .NET is currently handled on Windows desktop.
- zamalek 2y agoI guess another option would be to store the native code as an assembly manifest stream, and cast that to a delegate at runtime. That would achieve much the same thing as IJW without the proprietary bits.