JsonQueryStringSerializer top-level nullable support is broken - by Matt Davis

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 289415 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 7/27/2007 9:59:39 PM
Access Restriction Public


Nullable types can't be used in WebGet operation contracts when the enableWebScript behavior is turned on with webHttpBinding.  The ServiceHost starts up fine, but if a nullable value is omitted from the query string, the operation is not dispatched.

JsonQueryStringSerializer.CanConvert lies- it says it supports nullable types when asked, but ConvertStringToValue fails with a NullReferenceException when processing for a nullable.
I filed a suggestion about adding nullable support for WebHttpBehavior under feedbackID=289393, but this one seems like a bug, since JsonQueryStringConverter says it supports nullables when asked.
Sign in to post a comment.
Posted by Microsoft on 5/30/2008 at 5:58 PM

I wanted to make you aware that the issue you have reported was fixed in .NET Framework 3.5. Please continue to file great bugs such as these. We are releasing .NET Framework 3.5 SP1 in the next couple of monthes, please feel free to use our Connect site to file any feedback you have.


Erica Mohler
Microsoft Program Manager
Posted by Microsoft on 8/9/2007 at 1:49 PM
The development team agree that this is a bug in the beta - it is now on our list of things we'd like to fix before RTM.

This was a good catch - thanks!
Posted by Microsoft on 7/28/2007 at 1:15 AM
Thanks for your feedback. We have reproduced this bug on Visual Studio 2008 Beta 2, and we are sending this bug to the appropriate group within the VisualStudio Product Team for triage and resolution.

Thank you,
Visual Studio Product Team.
Posted by Microsoft on 7/27/2007 at 11:04 PM
Thank you for your feedback. We are currently investigating. If this issue is urgent, please call support directly (see http://support.microsoft.com).

Thank you,
Visual Studio Product Team