Conversation
|
Hey thx! I have a question regarding your change: does using attribute without compiler work on .Net Standard 2.0?
I believe it doesn’t? At least with StandardResolver they do not appear to work. I don’t see a way to register a resolver for my custom class without using compiler.
I would love to see this clarified :)
…Sent from my Phone
On Jun 14, 2021, at 5:56, Andrew Arnott ***@***.***> wrote:
In response to @bitinn's suggestion here: #471 (comment)
You can view, comment on, or merge this pull request online at:
#1264
Commit Summary
Clearly document unity scenarios that require AOT
File Changes
M README.md (7)
Patch Links:
https://github.com/neuecc/MessagePack-CSharp/pull/1264.patch
https://github.com/neuecc/MessagePack-CSharp/pull/1264.diff
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I meant attribute like DataContract or MessagePackObject. It seems like I have to use compiler code-gen on .Net Standard 2.0 + mono? Love to see a usage matrix to be honest.
…Sent from my Phone
On Jun 14, 2021, at 10:51, David Frank ***@***.***> wrote:
Hey thx! I have a question regarding your change: does using attribute without compiler work on .Net Standard 2.0?
I believe it doesn’t? At least with StandardResolver they do not appear to work. I don’t see a way to register a resolver for my custom class without using compiler.
I would love to see this clarified :)
Sent from my Phone
>> On Jun 14, 2021, at 5:56, Andrew Arnott ***@***.***> wrote:
>>
>
> In response to @bitinn's suggestion here: #471 (comment)
>
> You can view, comment on, or merge this pull request online at:
>
> #1264
>
> Commit Summary
>
> Clearly document unity scenarios that require AOT
> File Changes
>
> M README.md (7)
> Patch Links:
>
> https://github.com/neuecc/MessagePack-CSharp/pull/1264.patch
> https://github.com/neuecc/MessagePack-CSharp/pull/1264.diff
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I don't have the answers to your questions, as Unity isn't my area. Hopefully @neuecc can clarify. |
|
If you mean Custom class, and you want it to be automatically serializable for Custom class, it won't work. |
(I am on .Net Standard 2.0, instead of .Net 4.x) |
|
@bitinn: you need one formatter per type to be serialized. A formatter needs a resolver to find it. So at minimum for 10 types, you need 10 formatters and 1 resolver. |
In response to @bitinn's suggestion here: #471 (comment)