-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SerializationBinder and BindToName with Unity 2017 #22
Comments
Any solution? |
Same issue here. Both BindToName and BindToType are never called when using a custom Binder on Unity 2017 with Mono 4.6. |
Could really use a fix or workaround for this. |
There's a supported JSON.NET package on the asset store. It used to be paid, but the developer made it free after a deal. The developer from SaladLab (of this integration) has been missing for a long time now, so I don't recommend using it for new projects and, if possible, use the json solution from the asset store. |
Ah, ya that's actually what I'm using, and the bug is in their version. Sorry, I should have been more careful about looking at the owner of this branch. |
Ah, I see! Try sending an email to the developer (dustin at parentelement.com) or posting a reply in the asset's forum thread. Dev seems very responsive. He might even have a fix already, if others got the same issue before you. |
Hi,
I just updated my Unity to the 2017 version, in order to use a more recent (read not so old) version on the mono framework (version 4).
When working with custom SerializationBinder, one should be able to override both BindToName and BindToType methods.
But the fact is that BindToName seems not to be ever called.
Did I miss something, is it due to Json.Net.Unity3D assuming an 'old' version of mono, or is it a bug ?
The text was updated successfully, but these errors were encountered: