Yes. Typically interop is very straightforward. You look in the api docs and copy paste. Example here is the String doc[1]. Way down you see all the methods. S

Yes. Typically interop is very straightforward. You look in the api docs and copy paste. Example here is the String doc[1]. Way down you see all the methods. Some of the methods have overloads (multiple variants). Pretty straightforward here. (E.g. `"mystring".Contains("ring")`) Where it gets more verbose and finicky is when the API takes a C# callback. Even more complex is if it’s asynchronous so it takes a C# callback as a Task. An example being the `.Use` method for defining server middleware.[2] To see how it’s done, here’s a gist I found.[3] Notice how the function for requestHandler is verbosely annotated with Func<> and RequestDelegate, etc. Luckily this isn’t the norm, most APIs are less complicated. Even so, you write a wrapper (abstraction) around that complexity and only look at your wrapper. Which is why someone in this thread said to leave them in a dark corner. [1]: https://docs.microsoft.com/en-us/dotnet/api/system.string?view=net-5.0 https://docs.microsoft.com/en-us/dotnet/api/system.string?vi... [2]: https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.builder.useextensions.use?view=aspnetcore-5.0#Microsoft_AspNetCore_Builder_UseExtensions_Use_Microsoft_AspNetCore_Builder_IApplicationBuilder_System_Func_Microsoft_AspNetCore_Http_HttpContext_System_Func_System_Threading_Tasks_Task__System_Threading_Tasks_Task__ https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnet... [3]: https://gist.github.com/kspeakman/7870a75283f6942dd96ff34a03a612f8#file-program-fs-L27 https://gist.github.com/kspeakman/7870a75283f6942dd96ff34a03...