Dynamic property is null with endpoint routing about aspnetcoreodata HOT 4 CLOSED

@gathogojr Since it's related to your post, would you please take a look?

from aspnetcoreodata.

Sorry for the beginner questions. After switching to the Odata attribute routing. It worked for me. Thanks both for the help!

from aspnetcoreodata.

RouteAttribute is not used in OData attribute routing.
OData attribute routing is using [ODataRouteAttribute] and [ODataRoutePrefixAttribute].

from aspnetcoreodata.

@sunliangqin I hope you're able to make a distinction between following three things:

• ASP.NET Core attribute routing (using RouteAttribute - Route in short form),
• OData attribute routing (using ODataRouteAttribute and ODataRoutePrefixAttribute - ODataRoute and ODataRoutePrefix in short form respectively)
• Endpoint routing

Actions are either conventionally-routed or attribute-routed. Placing a route on the controller or the action (like you have done above) makes it attribute-routed, not endpoint-routed. However, you can either call MapControllers inside UseEndpoints to map attribute-routed controllers or call MapControllerRoute to map both conventionally-routed controllers and attribute-routed controllers.

You can read more about ASP.NET Core routing here and OData attribute routing here

I have added a sample service to the repo with endpoint routing enabled. If you changed this line in the client project,
from:

var serviceUri = new Uri("http://localhost:8302/odata");

to

var serviceUri = new Uri("http://localhost:1538/api");

you'll find everything works the same, with endpoint routing enabled.

from aspnetcoreodata.