.Net Client TypeNameHandling #1373

Closed
bjarteskogoy opened this Issue Jan 21, 2013 · 4 comments

3 participants

@bjarteskogoy

Make it possible to set the JsonSerializerSettings to use on the client.

@davidfowl
SignalR member

Moved to backlog.

@bjarteskogoy

Can I contribute in some way? Is there a planned solution for this?

@davidfowl
SignalR member

#530 is probably the closest thing to this. I'll close that one and opt for just allowing settings to be customized. Breaking the dependency on JSON.NET isn't something we care to do.

@davidfowl davidfowl was assigned Feb 23, 2013
@Xiaohongt
SignalR member

verified

@Xiaohongt Xiaohongt closed this Mar 8, 2013
@krishh86 krishh86 pushed a commit that referenced this issue Dec 22, 2013
@bjarteskogoy bjarteskogoy Ability to customize the JsonSerializer for a client connection
    - Connection class has JsonSerializer property
    - ConnectionExtensions has methods for serializing and deserializing using the serializer set on the connection
    - HubProxy tests provides a default serializer for IConnection.JsonSerializer {get; }
    - Added the test VerifyThatChangingTheJsonSerializerWorks

Issue: #1373
d6a611b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment