在OSX上使用make(Using make on OSX)

 我终于想出了一个解决方案。 这不是我会喜欢的（这将是返回特定的对象类型，并以某种方式指示WCF使用Json.Net序列化程序，而不是DataContractJsonSerializer），但它的工作非常好，它很简单明了。 
 
 使用这个新的解决方案来扩展我的例子： 
 
[WebGet(UriTemplate = "hello")]
public void SayHello()
{
    SimpleMessage message = new SimpleMessage() {Message = "Hello World"};
    string json = JsonConvert.Serialize(message);
    HttpContext.Current.Response.ContentType = "application/json; charset=utf-8";
    HttpContext.Current.Response.Write(json);
}
 
 注意void的返回类型。 我们不返回任何东西，因为它将被DataContractJsonSerializer序列化。 相反，我直接写入响应输出流。 由于返回类型为void，因此处理流水线未将content-type设置为默认类型“application / json”，因此我明确设置。 
 
 因为这使用了HttpContext ，所以我猜测它只有在您的服务类上有[AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Required)]才能工作，因为这将强制对服务的请求通过ASP.NET管道。 没有asp.net兼容性，HttpContext将不可用，因为wcf主机应该是主机不可知的。 
 
 使用这种方法，结果在GET请求的firebug中看起来很完美。 正确的内容类型，正确的内容长度和raw json，不包含在引号中。 而且，我正在使用Json.Net来获得序列化。 两全其美。 
 
 当我的服务方法具有[DataContract]对象类型作为输入参数时，我并不是100％肯定了我可能遇到的关于序列化的障碍。 我假设DataContractJsonSerializer也将被用于。 当我来到它时，会穿过这座桥，如果它造成了一个问题。 迄今为止，我的简单DTO还没有。 
 
 更新请参阅Oleg的答案（UPDATE2部分）。 他将服务方法的返回类型从void更改为System.ServiceModel.Channels.Message ，而不是使用HttpContext.Current.Response.Write() ，他使用： 
 
return WebOperationContext.Current.CreateTextResponse (json,
    "application/json; charset=utf-8", Encoding.UTF8);
 
 这确实是一个更好的解决方案。 谢谢奥列格 
 
 更新2还有另一种方法来实现这一点。 将您的服务的返回类型从消息更改为流，然后返回： 
 
WebOperationContext.Current.OutgoingResponse.ContentType = "application/json; charset=utf-8";
return new MemoryStream(System.Text.Encoding.UTF8.GetBytes(json));
 
 我没有做任何具体的测试，但是这可能是可能返回大量数据的方法的更好的选择。 我不知道这是非常重要的非二进制数据。 无论如何，一个想法。 

I finally figured out a solution to this. It's not what I would have preferred (which would be to return the specific object type, and somehow instruct WCF to use a Json.Net serializer, instead of the DataContractJsonSerializer), but it is working great, and it's simple and clear.
 
Extending my contrived example using this new solution:
 
[WebGet(UriTemplate = "hello")]
public void SayHello()
{
    SimpleMessage message = new SimpleMessage() {Message = "Hello World"};
    string json = JsonConvert.Serialize(message);
    HttpContext.Current.Response.ContentType = "application/json; charset=utf-8";
    HttpContext.Current.Response.Write(json);
}
 
Note the return type of void. We do not return anything, since it would be serialized with DataContractJsonSerializer. Instead, I write directly to the response output stream. Since the return type is void, the processing pipeline doesn't set the content-type to the default type of "application/json", so I set it explicitly.
 
Because this uses HttpContext, I'm guessing it will only work if you have [AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Required)] on your service class, since that will force requests to the service to go through the ASP.NET pipeline. Without the asp.net compatibility, the HttpContext will not be available, since wcf hosting is supposed to be host agnostic.
 
Using this method, the results look perfect in firebug for GET requests. Correct content-type, correct content length, and raw json, not wrapped in quotes. And, I'm getting the serialization I want using Json.Net. Best of both worlds.
 
I'm not 100% positive of what obstacles I might run into regarding deserialization, when my service methods have [DataContract] object types as input parameters. I'm assuming the DataContractJsonSerializer will be used for that too. Will cross that bridge when I come to it...if it creates a problem. It hasn't so far, with my simple DTOs.
 
UPDATE See Oleg's answer (the UPDATE2 part). He changes the return type of the service method from void to System.ServiceModel.Channels.Message, and rather than using HttpContext.Current.Response.Write(), he uses:
 
return WebOperationContext.Current.CreateTextResponse (json,
    "application/json; charset=utf-8", Encoding.UTF8);
 
Which is indeed a better solution. Thank you Oleg.
 
UPDATE 2 There is yet another way of accomplishing this. Change your service's return type from Message to Stream, and return this:
 
WebOperationContext.Current.OutgoingResponse.ContentType = "application/json; charset=utf-8";
return new MemoryStream(System.Text.Encoding.UTF8.GetBytes(json));
 
I haven't done any specific tests, but it's possible that this would be a better choice for methods that could potentially return large amounts of data. I don't know if that matters for non-binary data though. Anyway, a thought.