aspnet-api-versioning: Configuring entity as both Singleton and EntitySet causes 404 on functions

Consider the following configuration.

var myFunctionConfiguration = builder
    .Singleton<User>("Me")
    .EntityType
    .Function("MyFunction")
    .Returns<User>();
myFunctionConfiguration.Parameter<DateTime>("begin");
myFunctionConfiguration.Parameter<DateTime>("end");

builder
    .EntitySet<User>("Users");

This will function properly without using versioning. However as soon as I enable versioning /Me/MyFunction(begin=2001-01-01,end=2019-02-04) returns a 404.

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 17

Most upvoted comments

It would appear that you’re satisfied with the final result; especially considering you already had your own workaround. I believe we’ve driven this to conclusion with a complete end-to-end, working solution. If your issue has not be resolved or you have more questions, feel free to come back or reopen the issue. Thanks.

commonsensesoftware on Jul 8, 2019