WCF Rest JSON Serialization

I am planning to use WCF rest JSON.  In past I have seen serialization issues it.  I read people using newtonsoft.json as default serializer

I see some explanation below of using it. I need some example where we I can use with newtonsoft.json . also want to handle throw back http errors to the client


One more question Other have to host on windows service so going with WCF . I dont tjhink Web api is solution here??

Who is Participating?
Alexandre SimõesManager / Technology SpecialistCommented:
Yep, definitely.
In your case I go WebAPI without a doubt.

What kind of issue did you have regarding the null values?
Null on the inputs or on the output?
Alexandre SimõesManager / Technology SpecialistCommented:
WCF vs WebAPI really depends on what you want.

If you want to do a "simple" REST service then go with WebAPI, hand down. When I say "simple" is architectural simplicity, business wise there's no limitation.

If you want to have a more advanced implementation, supporting SOAP and REST endpoints, or realy put your hands on how the communication is done at a lower level, then WCF is the way to go.

From what I see on your tags, you want to implement a REST service so, in that case, go for WebAPI, it's all you need in terms of functionality and already serializes your responses to JSON without any problems.

Member_2_7967608Author Commented:
Hi Alex

Thanks for the comments. My consumer is AngularJS.

I want to host in IIS Web api or WCF Rest. Here are some more details

1. I have to host 2 methods. One for GET and other For Update.
2.  The GET method invoke 3 ext services to get the data and finally gets data.
3. One issue I had earlier is with the DataContract Serializer of WCF. I had to use Json.NET Serializer to handle null values and ignore.

So Web api would be better choice, right?
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Member_2_7967608Author Commented:
I want to ignore Properties with Null to serialize to Json. I think the default Serializer does not let us do that.   Also If some properties we dont want to serialize and ignore we cant implement it.
Alexandre SimõesManager / Technology SpecialistCommented:
WEBAPI allows you to control the serialization through what they call formatters, and in your case is pretty simple. Should be something like:
 config.Formatters.JsonFormatter.SerializerSettings.NullValueHandling = NullValueHandling.Ignore

Open in new window

Member_2_7967608Author Commented:
Thanks so much.

One last question,  in  Web Api I need to use some proxy URLs from the APP.config.


    <add key="URL1" value="http://test2" />
    <add key="URL2" value="http://test2" />

1. Should I create a Static class and use those URLs.
   Since the Webapi is stateless. So for every call it will make configuration access.
   I am checking for any performance issues on service hits.

2. Or I can pass it in the Angularjs Request body these 2 URLs everytime.

3. Is there any other mechanism?
Alexandre SimõesManager / Technology SpecialistCommented:
Hi mate,
what do you mean by proxy URLs?

What are you trying to achieve? Reverse proxy for the AngularJS ajax calls?
Member_2_7967608Author Commented:
The Webapi will be calling to 2 external soap web services.  They have 2 address endpoints.

 So I need to have the soap endpoints  of the services because they change based on dev or test environment.

<I was trying to simplify this as URL in my message>
Member_2_7967608Author Commented:
Let me know you need further clarification.
Alexandre SimõesManager / Technology SpecialistCommented:
Oh, ok, got it now.

Yes, the best is to put that kind of config in the web.config file as appSettings as you did in your sample.
Then you can just add one config per environment and use XML transformations to add the correct values depending on the environment you're building to.

Another approach is to put that config in the server (host) configuration, as a server variable of something like that.
This is what I do when I want to promote packages throughout environments instead of packaging each all the environment configs in plain text inside (some I might not want the devs to know).
With this approach, instead of picking the config from the web-config you just pick it from the configuration on the server.
This is a lot less usual to find but definitely the way to go if you're serious about continuous delivery stuff :)

I guess I went a bit off track on you here, sorry :), but I think this second option is good information for you to keep in the back of your head for possible future usage.

Cheers mate!
Member_2_7967608Author Commented:
Thank you Alex.

I have option to store  on web.config.

I guess my question was based on performance. Are the config values stored in IIS worker process for this app memory or they are initiated with Every request.
Alexandre SimõesManager / Technology SpecialistCommented:
Well, it's fair to be said that reading values from web.config shouldn't be a performance issue unless you're really hammering that service like mad.
Anyway, if you read those values on the global.asax and put them in a static config object, then you're set. Basically, they will be loaded into memory throughout the lifecycle of the application pool.

So, use the application_start method on the global.asax to load your settings and put them in a static configuration variable of class.

That's it :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.