Skip to content

[C#] Fury support for C# #686

@jiangguilong2000

Description

@jiangguilong2000

for unity game development

Activity

changed the title [-]Looking forward to supporting C# as much as possible[/-] [+][C#] Fury serialization support for C#[/+] on Jul 18, 2023
chaokunyang

chaokunyang commented on Jul 18, 2023

@chaokunyang
Collaborator

@jiangguilong2000 Thanks for submitting this issue. As a multi-language serialization framework, c# support is important for fury. But we don't have experience for c#. Maybe someone in the community are interested to take this issue.

iceboundrock

iceboundrock commented on Jul 20, 2023

@iceboundrock

C#/.net already has a good foundation for this, like Expression Trees, which can save quite a lot of effort. I am working on a very preliminary C# port on top of Fury java implementation, but I cannot commit to anything yet.

chaokunyang

chaokunyang commented on Jul 21, 2023

@chaokunyang
Collaborator

C#/.net already has a good foundation for this, like Expression Trees, which can save quite a lot of effort. I am working on a very preliminary C# port on top of Fury java implementation, but I cannot commit to anything yet.

@iceboundrock that would be very great, looking forward to it. Let us know if there are anything we can help. We're formalize our cross language protocol into a text spec. But it may still take some time. The csharp poc can skip protocol alignment and do it in the future

nfsfairytale

nfsfairytale commented on Sep 11, 2023

@nfsfairytale

hope support c#

pinned this issue on Oct 8, 2023
changed the title [-][C#] Fury serialization support for C#[/-] [+][C#] Fury support for C#[/+] on Oct 8, 2023
chaokunyang

chaokunyang commented on Oct 8, 2023

@chaokunyang
Collaborator

hope support c#

Glad to see more demands for this, pined the issue to prioritize it!
Hope this can help it get supported sooner.

unpinned this issue on Oct 20, 2023
pinned this issue on Oct 20, 2023
jpfed

jpfed commented on Oct 26, 2023

@jpfed

@iceboundrock Expression trees sound like a great idea for selectively deserializing fields. On the serialization end, it may be worth considering source generators for optimum performance.

chaokunyang

chaokunyang commented on Oct 26, 2023

@chaokunyang
Collaborator

@jpfed How about generate code at runtime? Generate source code statically will need users to integrate it with build pipeline, which may introduce extra user mind burden.

chaokunyang

chaokunyang commented on Apr 18, 2024

@chaokunyang
Collaborator

https://fury.apache.org/docs/specification/fury_xlang_serialization_spec is our cross-language serialization spec, anyone interested at this issue can take a look at this document to know how to implement C# for fury

chaokunyang

chaokunyang commented on Aug 19, 2024

@chaokunyang
Collaborator

C#/.net already has a good foundation for this, like Expression Trees, which can save quite a lot of effort. I am working on a very preliminary port on top of Fury java implementation, but I cannot commit to anything yet.C#

I would like to know the progress of C# porting. We can form a small team to promote this matter together, as the addition of C# serialization is crucial for Unity game development. After all, Fury is far superior to other serialization options.

Hi @nfsfairytale , this hasn't been started. I can help break the work down, But I am not familiar with c# and busy with other things recently, thus can't take up part of the work

unpinned this issue on Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @jpfed@iceboundrock@jiangguilong2000@nfsfairytale@chaokunyang

        Issue actions

          [C#] Fury support for C# · Issue #686 · apache/fory