title: MultipleApiVersions with Swagger
body: <p>I am trying to enable versioning on a REST API, where the version is specified in the header, as <code>"api-version":2</code>, vendor media type, as <code>"accept: application/vnd.company.resource-v2+json</code>, <code>application/json; version=2"</code>, or in a query string <code>"?version=2"</code>.  The implementation is using IHttpRouteConstraint and RouteFactoryAttribute.  This works perfectly.  However, Swagger is not able match the right model with the correct versioned document.  The operationId is always from the version 1 model.</p>
  
  <pre><code>public class DevicesController : ApiController
  {
      [HttpGet, RouteVersion( "api/devices", 1, Name = "v1.devices" )]
      [ResponseType( typeof( IEnumerable&lt;Models.V1.Device&gt; ) )]
      public IHttpActionResult GetV1( )
      {
          return Ok( new List&lt;Models.V1.Device&gt; { ... } );
      }
  
      [HttpGet, RouteVersion( "api/devices", 2, Name = "v2.devices" )]
      [ResponseType( typeof( IEnumerable&lt;Models.V2.Device&gt; ) )]
      public IHttpActionResult GetV2( )
      {
          return Ok( new List&lt;Models.V2.Device&gt; { ... } );
      }
  }
  </code></pre>
  
  <p>Swagger docs for V2 has the wrong operationId and MIME Types.</p>
  
  <pre><code>"tags":
  [
      "Devices"
  ],
  "summary": "Get a list of device(s) by the device identifier",
  "operationId": "Devices_GetV1",
  "consumes": [ ],
  "produces": 
  [
      "application/vnd.safe.inventory-v1+json",
      "application/json",
      "text/json",
      "application/vnd.safe.inventory-v1+xml",
      "application/xml",
      "text/xml"
  ],
  ...
  </code></pre>
  
  <p><strong>Swashbuckle 5.2.2</strong></p>
  
  <p>I have tried customizing the ApiExplorer as descripted in these post:</p>
  
  <pre><code>github.com/domaindrivendev/Swashbuckle/issues/558
  github.com/domaindrivendev/Swashbuckle/issues/317
  </code></pre>
  
  <p>I have also tried building a custom selector.</p>
  
  <p>I also went down this route as well, but I don’t think that is the same issue.
  <a href="https://azure.microsoft.com/en-us/documentation/articles/app-service-api-dotnet-swashbuckle-customize/" rel="nofollow">https://azure.microsoft.com/en-us/documentation/articles/app-service-api-dotnet-swashbuckle-customize/</a></p>
  
  <p>Asking for any direction any help would be appreciated.</p>
  
  <p>Thanks in advance.</p>