Source code checked in, #6abf442f09a1
OData formatter: Incorporate code review feedback.
View ArticleSource code checked in, #e37a5a2be6eb
[OData] Encode characters when necessary in ODataLink direct path
View ArticleSource code checked in, #60f4d8586981
[OData] Use entity set name instead of controller name to build Location header link for EntitySetController POSTs
View ArticleCommented Issue: Some characters are not encoded from odata link generation...
This is a regression issue with recent changes.+, ? are not encoded in selfhost. Web host will be blocked by security rules, so not applicable.# is not encoded in both selfhost and webhost and it...
View ArticleEdited Issue: Some characters are not encoded from odata link generation [753]
This is a regression issue with recent changes.+, ? are not encoded in selfhost. Web host will be blocked by security rules, so not applicable.# is not encoded in both selfhost and webhost and it...
View ArticleCommented Issue: Use entity set name instead of controller name to build link...
The only place that uses controller name to build link is at EntitySetControllerHelpers.cs(79). public static HttpResponseMessage PostResponse<TEntity, TKey>(ApiController controller, TEntity...
View ArticleEdited Issue: Use entity set name instead of controller name to build link [765]
The only place that uses controller name to build link is at EntitySetControllerHelpers.cs(79). public static HttpResponseMessage PostResponse<TEntity, TKey>(ApiController controller, TEntity...
View ArticleSource code checked in, #d302f9b77a3f
Issue 767: ODataError should serialize ModelState errors. Converting model state errors to a human readable string and putting them in the odata inner error.
View ArticleCommented Issue: ODataError should serialize ModelState errors. [767]
without this debugging exceptions thrown in odata formatter are hard to debug.Comments: http://aspnetwebstack.codeplex.com/SourceControl/changeset/d302f9b77a3f
View ArticleEdited Issue: ODataError should serialize ModelState errors. [767]
without this debugging exceptions thrown in odata formatter are hard to debug.
View ArticleSource code checked in, #5bcc14ab69de
Issue 560: Required navigation property has ZeroOrOne multiplicity on edm model
View ArticleCommented Issue: Required navigation property has ZeroOrOne multiplicity on...
Here is the test code:[DataContract] public class SimpleDataContractModel{[Key][DataMember] public int KeyProperty { get; set; }[DataMember] public string Name { get; set; }[Required][DataMember]...
View ArticleEdited Issue: Required navigation property has ZeroOrOne multiplicity on edm...
Here is the test code:[DataContract] public class SimpleDataContractModel{[Key][DataMember] public int KeyProperty { get; set; }[DataMember] public string Name { get; set; }[Required][DataMember]...
View ArticleEdited Issue: Creating links to other OData routes is hard [771]
I have to figure out the appropriate path handler to use. The framework already knows which path handler should be used when I provide a route name; it shouldn't ask me for it.
View ArticleCommented Issue: Creating links to other OData routes is hard [771]
I have to figure out the appropriate path handler to use. The framework already knows which path handler should be used when I provide a route name; it shouldn't ask me for it.Comments: This is a valid...
View ArticleCommented Issue: Provide support for specifying required action parameter...
Currently the [Required] attribute can be used on properties but not on the type itself or on the parameter. So when sending a request with empty body to the POST action below, the ModelState.IsValid...
View ArticleSource code checked in, #ea64fc86b54d
Parameterize $skip and $top values for better performance.
View Article