Chris Martinez

@knightian is that a question? Looks like you are probably missing a `using` directive. The recommended statements are: ```c# using Asp.Versioning; using Asp.Versioning.Conventions; ```

Yeah, it's unfortunate, but the much of the implementation for the API Explorer (**Microsoft.AspNetCore.Mvc.ApiExplorer**) depends on **Microsoft.AspNetCore.Mvc.Core**. I'm not entirely sure why that is, but it's a decision that was...

`6.0` has been officially released and contains the workaround. In terms of the original question, that should address it. I can't control when the ASP.NET Core will eventually provide a...

@jamesfoster This is happening because you are missing the route constraint. You have: ```c# [Route("/v{apiVersion}")] ``` but it needs to be: ```c# [Route("/v{version:apiVersion}")] ``` `apiVersion` is the default name of...

Are you able to show at least the skeleton of the rest of your controller and perhaps the configuration setup? Which route/action is giving you trouble? You seem to indicate...

This provides a little more about the action, but it doesn't provide any information about the controller or application setup. I still have a number of questions. 1. Are you...

This makes a lot more sense. Out of curiosity, does this work without versioning? I would **not** expect it to. `[Produces("application/json")]` means that the action allows `Accept: application/json` and `[Consumes("application/merge-patch+json")]`...

Thanks for confirming. I'll see what I can find.

My opinionated dogma aside 😉 , I'm not able to repro your scenario. I've tried against the latest `5.0.0` release and back to `4.1.1`. I'm not sure if you have...

I'll reiterate that `application/merge-patch+json` is **only** meant for the `PATCH` method. Here's what I added: ```c# /// /// Updates an existing order. /// /// The order to update. /// The...