Building against .NET 7 and above

[pnorman63]

Hi there!

It's more than possible that I'm missing something, but I hope you can help.

I'm working on a C# code base targeted at .NET 7, and using Neo4j. I'm investigating replacing Neo4j with KuzuDB as our graphs are not that big and I'm hoping KuzuDB will be quicker and simplify our architecture.

My issue is, should the kuzunet.dll and kuzu_shared.dll work with .NET 7, or do I need new versions of these? If so how can I obtain them?

I've created a solution to builld KuzuDB-Net targeting .NET 7.0, but I think kuzunet.dll and kuzu_shared.dll are incompatible with this.

Thanks for any help you might be able to provide.

Paul

[kidneyhex]

In case it helps anyone in the future finding this:

I've made a rough fork updating to KuzuDB 0.8.2 and adding a project & example targeting .NET 9.0.

I don't intend to PR this, it's just experimental code for now:

https://github.com/thinkpoop/KuzuDB-DotNetInterface-Core/tree/rough-draft

My future plan is to write wrappers around the SWIG classes to make them more like the other KuzuDB APIs, and more .NET friendly.

[gregorvilkner]

@thinkpoop - have you got a working example for 0.11? Cheers, Gregor

[kidneyhex]

@gregorvilkner I haven't yet, but will give it a try this weekend.

[gregorvilkner]

Meanwhile, I did manage to use CSnakes and the Python sdk in a Blazor Server app and got that successfully running on an Azure app service... I'll need to do some more use cases and testing, but this could also be a viable access route for using Kuzu on the .net stack.

[kidneyhex]

@gregorvilkner I've got it updated for 0.11.1

I also added a readme-too.md and my batch files to try to give some idea on what I do to update it. It's basically the same as the readme, just with the batch files helping automate parts.

Wrapping a version of the SDK that Kuzu maintains themselves isn't a terrible plan.

In my case, I wanted to avoid too many extra layers since my corporate environment is kind of locked down for security, and all I needed was the basic parts of kuzu. But of course I got pulled into other projects, so I haven't been working on this at all. =P

[gregorvilkner]

@thinkpoop, only recently managed to take a look at this. thank you so much for doing this upgrade, works great. @FactEngineCommunity, can this be consolidated? otherwise, kuzu folks should probably reference the thinkpoop repo. Cheers, Gregor

[kidneyhex]

I've created a new wrapper from scratch with the last version of KuzuDB:
https://github.com/KuzuDot/KuzuDot

The library targets .NET Standard 2.0 and .NET 8.0, so it will work with both branches of .NET.

It supports everything in the KuzuDB DLL that I could (apache arrow, complex structures, every data type...).

Since KuzuDB went into archive mode yesterday, I don't have to worry about the native side changing I guess 😢

[FactEngineCommunity]

Awesome. Good work. I'm surprised to hear about KuzuDB. If only they had stuck with it...

[gregorvilkner]

@thinkpoop - did you remove the oowraper?

[kidneyhex]

@thinkpoop - did you remove the oowraper?

If you mean the .net core version of the kuzunet, yes and no. I switched the kuzunet library to use .NET Standard, so there don't need to be 2 versions.

So if you were referencing the Core stuff, you can just use the kuzunet.

[gregorvilkner]

@thinkpoop - did you remove the oowraper?

If you mean the .net core version of the kuzunet, yes and no. I switched the kuzunet library to use .NET Standard, so there don't need to be 2 versions.

So if you were referencing the Core stuff, you can just use the kuzunet.

We saw a bunch of KuzuDB-OOWrapper projects referencing KuzuDB-NetCore.csproj last week in the "rough-draft" branch. Ok, we'll use the .NET Standard reference. Thanks a lot for your help.

[kidneyhex]

Ooh, I didn't mean to push that to the rough-draft branch.

That's my version zero of KuzuDot, where I tried letting copilot wrap kuzunet. It's completely unreviewed AI generated code, so... 🤷

If you want it, it's still in the poorly named simplified-swig-interface branch now: https://github.com/thinkpoop/KuzuDB-DotNetInterface-Core/tree/simplified-swig-interface

KuzuDot is basically the same OOWrapper plan, but I've reviewed it a lot more and made sure it works as intended. And I plan to keep maintaining it, unless the KuzuDB creators come out with a KuzuDB 2.0 that's better and not compatible.

[gregorvilkner]

@kidneyhex, what's the difference between the simplified-swig-interface and the dotnet-standard branches? is there a plan to bump either of those to main? we've been using this in .net core projects and it works very well. also, since the dust settled a bit, i've left a note on the graphgeeks->ladybugdb channel: https://discord.com/channels/1162999022819225631/1427801531331248251/1468990651822641312

[kidneyhex]

@gregorvilkner

The "simplified-swig-interface" was just me testing things. I don't remember much besides that I had started trying to make an object oriented wrapper to make it more C#-friendly.

The "dotnet-standard" branch is more just updating the swig results to .NET Standard 2.0 so they can be used in Framework 4.8+ or .NET core.

If I was going to push any, it'd be the dotnet-standard.

I didn't plan on though, since I don't know what FactEngine would like for PRs, it seemed kind of dead here.

[FactEngineCommunity]

Hi, I'm not doing more work on this. So if you/the-community want this repo to point to a fork that's more up to date, I'm happy to do that. There seems to be genuine interest in keeping this alive. Personally, I don't have the c/swig skills to keep it alive (original version was from a contractor I paid to build the interface). So if someone wants to take this project on...there's no holding back from this end.