Microsoft solving the unsafe interop debacle by introducing a "safe" keyword is the funniest shit I've ever seen dude devblogs.microsoft.com/dotnet/impro...

Node.js addons… in C#. Native AOT lets you export napi_register_module_v1, call N‑API via LibraryImport("node"), use spans + stackalloc for zero‑alloc UTF‑8, and ship shared libs without node‑gyp or Python. Clean interop, faster onboarding, fewer toolchains.
Read → ift.tt/2mz8B1E

If you just put "fmod" in the DllImport/LibraryImport instead of "fmod.dll" then it should run just as well on Linux with minimal rework: dotnet will automatically append ".dll" on Windows, ".so" on Linux. I think it also tries .dynlib on MacOS, but you're probably not going to be building for that.

All three I guess? Happy to tell people about how ILGPU and OpenGL work great on Linux, how DllImport and LibraryImport work as normal.

Node.js addons… in C#? Yep. Native AOT lets you ship shared libs that plug straight into N‑API, no node‑gyp, no Python installs, no C++ detours. Clean interop with UnmanagedCallersOnly, LibraryImport, spans, and zero‑alloc UTF‑8 marshalling.
Read the blog → ift.tt/2mz8B1E

LibraryImport was working properly with NET8 but not anymore with NET9 (109946) https://github.com/dotnet/runtime/issues/109946

Writing Node.js addons with .NET Native AOT

Is [LibraryImport] always faster than [DllImport]? Not necessarily.
I benchmarked both across native Windows API calls, string marshalling, handles, out parameters, and allocation-heavy scenarios. The results may surprise you.
#dotnet #csharp #performance #MVPBuzz
dotnettips.com/2026/08/02/p...

Create error on LibraryImport of generic delegate (114827) https://github.com/dotnet/runtime/pull/114827

Using [LibraryImport] with a generic delegate parameter (e.g. Func) causes an exception (113590) https://github.com/dotnet/runtime/issues/113590

irrelevant for LibraryImport.

Alternatives:
- https://github.com/microsoft/CsWin32
- https://github.com/dotnet/pinvoke

To my future self: apparently, LibraryImport wasn't event meant to be compatible with DllImport: https://github.com/dotnet/runtime/blob/main/docs/design/features/source-generator-pinvokes.md#:~:text=change%20for%20the%20developers.

Which renders <a href="http://pinvoke.net" class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">http://pinvoke.net signatures mostly...

Changed DllImport to LibraryImport (as was persistently suggested by the IDE), and my app started crashing randomly in unrelated places.

All interop signatures are coming from battle-tested <a href="http://pinvoke.net." class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">http://pinvoke.net.

My take: don't fix what ain't broken.
#csharp #dotnet

For some years I've been demonstrating creating hard links with PInvoke/LibraryImport on Windows and Linux, now it's part of .NET 11: github.com/dotnet/core/... What should I use next what's not included with .NET? #dotnet

There are just some instances where LibraryImport for P/Invoke isn’t the solution, huh…

Writing Node.js addons with .NET Native AOT

Breakpoints in libraryimport cpp code while running dotnet test https://old.reddit.com/r/dotnet/comments/1qhbzd2/breakpoints_in_libraryimport_cpp_code_while/

#dotnet

No LibraryImport or DllImport too?

Importing your whole library? It only takes a few clicks!

#Bookerei #BookereiApp #LibraryImport #EasyMigration #BookManagement #JustAFewClicks #DigitalLibrary #ReadingMadeEasy #BookLovers #EffortlessImport #BookApp #BookOrganization #ReadWithBookerei

As dlopen/dlsym cannot work on .NET wasm, and the only way to interop is through DllImport/LibraryImport, which means that having a GL class specialized for Wasm would be required. Did you create something of that sort?