1

Closed

Make ODataQueryOptions behave more like a property

description

As of right now, every time the user calls EntitySetController.QueryOptions we create a new instance of ODataQueryOptions<T>.

This causes some problems when the user calls it several times and makes changes on one of the instances as the customer expects the same instance to be returned every time he calls EntitySetController.QueryOptions.
Closed Oct 3, 2013 at 10:25 PM by danroth27
We now recommend deriving directly from ODataController (ex. using our new OData scaffolder), and then binding to the query options as a parameter.

comments

jacalvar wrote May 22, 2013 at 11:29 PM

Also, use the EdmModel and the information on the request to figure out the right type to use to create the ODataQueryOptions instead of using the generic type on the EntitySetController.