WIP: dotnet binding project #492
Conversation
havarnov
commented
Oct 30, 2025
havarnov
commented
- uses csbindgen to automatically create cs bindings
- adds a nuget package
havarnov
force-pushed
the
feature/dotnet-bindings
branch
3 times, most recently
from
72499b2 to
f32ce6a
Compare
|
Oh wow! I haven't thought about this, but could be great!!! |
havarnov
force-pushed
the
feature/dotnet-bindings
branch
from
e30c326 to
d1805e2
Compare
|
@nhatcher the rust side of this binding would be equivalent to how a c binding would look, nothing dotnet specific about it. Would you prefer to split it into a c binding project? I guess that also can be done at a later stage if necessary/requested. |
I don't know, to be honest. I actually don't have much experience with dotnet :) |
Yes, nuget.org is Microsofts official package repository. |
Sure. I’ll ping you when it’s ready for review. |
havarnov
force-pushed
the
feature/dotnet-bindings
branch
21 times, most recently
from
baf7e80 to
27fd7d1
Compare
havarnov
force-pushed
the
feature/dotnet-bindings
branch
12 times, most recently
from
51144c9 to
b801f0a
Compare
* uses csbindgen to automatically create cs bindings * adds a nuget package
* Multiple target frameworks. * Fix a couple of memory issues. * Documentation.
havarnov
force-pushed
the
feature/dotnet-bindings
branch
from
b801f0a to
d903f70
Compare
|
@nhatcher this is now ready for review. I decided to aim for a very simple 0.0.1-beta1 release with few features. But the developer experience, build, CI should all be good to go. Just to be clear, I'm totally fine with you not wanting this bindings in this repo if you don't want to increase the complexity of the project or whatever. It's possible to keep this in a separate repo. |
|
Let's see! I will have a look at it. I will learn something for sure |
2 participants
