Add Nullable support to System.ServiceModel.Dispatcher.QueryStringConverter - 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 289393 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 7/27/2007 6:18:15 PM
Access Restriction Public


System.ServiceModel.Dispatcher.QueryStringConverter (and by extension, WebGet/WebInvoke-style WCF operations) would be more useful if Nullable<T> were supported conversion types.
Sign in to post a comment.
Posted by BabbuP on 2/10/2014 at 11:57 AM
This still continues to be a problem for me, it says that this bug is fixed. I am using .net 4.5
Posted by codan3 on 10/27/2010 at 1:34 PM
How is this still not supported?
Posted by Microsoft on 8/9/2007 at 1:49 PM
We've taken this to the development team, and they agree. This is now on our list of things we'd like to fix before RTM.

Thank you very much for this input. Your feedback really helps - keep it coming!
Posted by Microsoft on 8/6/2007 at 5:52 PM
Thanks for your feedback. We have routed this suggestion to the appropriate group within the Visual Studio Product Team for triage and resolution.

Thank you,
Visual Studio Product Team.
Posted by Microsoft on 8/6/2007 at 4:56 PM
Thank you for your feedback. We are currently investigating. If this issue is urgent, please call support directly (see

Thank you,
Visual Studio Product Team