Wrong property navigation action is selected in ODATA controllers

[GennadyGS]

When there are multiple navigation actions in ODATA controller, first one (based on method order in class) is always executed regardless of requested navigation property.

Example (can be verified in ODataBasicSample):

    [ODataRoutePrefix( "People" )]
    public class People0Controller : ODataController
    {
        [ODataRoute( "({id})/FirstName" )]
        public IActionResult GetFirstName( [FromODataUri] string id, ODataQueryOptions<Person> options ) =>
            Ok( new { FirstName = $"{id}-first-name" } );

        [ODataRoute( "({id})/LastName" )]
        public IActionResult GetLastName( [FromODataUri] string id, ODataQueryOptions<Person> options ) =>
            Ok( new { LastName = $"{id}-lastName" } );
   }

Request:
http://localhost:1238/api/People(1)/LastName?api-version=1.0

Actual response:

{
    "firstName": "1-first-name"
}

Expected response:

{
    "lastName": "1-last-name"
}

[commonsensesoftware]

Thanks for reporting it. I'll have a look.

[fusionshen]

The same to me.
If you have two [HttpGet] actions no matters what [ODataRoute("****")](in a same pattern) is, the route will match the first one.
Like this:
[HttpGet("IsAuthenticated"), HttpPost("IsAuthenticated")]
[ODataRoute("IsAuthenticated")]
public bool IsAuthenticated(){...} <=======Actual response.

[HttpGet("GetUserInfo"), HttpPost("GetUserInfo")]
[ODataRoute("GetUserInfo")]
public IActionResult GetUserInfo(){...}<=======Expected response.

[mmckenz]

I am witnessing a similar issue with a single controller offering multiple collections.

public class SampleODataController : ODataController
{
    [EnableQuery]
    [ODataRoute("Foos")]
    public IQueryable<Foo> GetFoos()
    {
        return new List<Foo>().AsQueryable();
    }

    [EnableQuery]
    [ODataRoute("Bars")]
    public IQueryable<Bar> GetBars()
    {
        return new List<Bar>().AsQueryable();
    }
}
...
public IServiceProvider ConfigureServices(IServiceCollection services)
{
    ...
    services.AddMvc();
    services.AddOData();
    ...
}
...
public void Configure(IApplicationBuilder app, IHostingEnvironment env, IApplicationLifetime appLifetime)
{
    ...
    app.UseOData(MyEdmModel.GetEdmModel());
    ...
}

The above works using the standard ASP.NET Core OData config. I can hit /odata/Foos or /odata/Bars and the appropriate controller method is called as expected.

When configured to use ASP.NET Core OData versioning as follows, the first method of the controller is hit for both /v1/Foos and /v1/Bars.

[ApiVersion("1.0")]
public class SampleODataController : ODataController
{
    [EnableQuery]
    [ODataRoute("Foos")]
    public IQueryable<Foo> GetFoos()
    {
        return new List<Foo>().AsQueryable();
    }

    [EnableQuery]
    [ODataRoute("Bars")]
    public IQueryable<Bar> GetBars()
    {
        return new List<Bar>().AsQueryable();
    }
}
...
public IServiceProvider ConfigureServices(IServiceCollection services)
{
    ...
    services.AddMvc();
    services.AddApiVersioning();
    services.AddOData().EnableApiVersioning();
    ...
}
...
public void Configure(IApplicationBuilder app, IHostingEnvironment env, IApplicationLifetime appLifetime, VersionedODataModelBuilder modelBuilder)
{
    ...
    app.UseMvc(routes =>
    {
        routes.MapVersionedODataRoutes(
            ODataApplicationBuilderExtensions.DefaultRouteName,
            "v{version:apiVersion}",
            modelBuilder.GetEdmModels());
    });
    ...
}

It seems the ODataRoute attribute is ignored with the versioned implementation.

[GennadyGS]

Thanks a lot for fixing.
When is it going to be published to nuget?