Skip to content
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

Open
cchafer opened this issue Jun 20, 2017 · 6 comments
Open

SerializationBinder and BindToName with Unity 2017 #22

cchafer opened this issue Jun 20, 2017 · 6 comments

Comments

@cchafer
Copy link

cchafer commented Jun 20, 2017

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 ?

@ghost
Copy link

ghost commented Nov 16, 2017

Any solution?

@MikeL1300
Copy link

MikeL1300 commented Nov 28, 2017

Same issue here. Both BindToName and BindToType are never called when using a custom Binder on Unity 2017 with Mono 4.6.

@dfraska
Copy link

dfraska commented May 16, 2018

Could really use a fix or workaround for this.

@SugoiDev
Copy link

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.

PARENTELEMENT, LLC JSON .NET For Unity

@dfraska
Copy link

dfraska commented May 17, 2018

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.

@SugoiDev
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants