Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Swashbuckle.Core - Method MapHttpRoute not found

See original GitHub issue

I’ve installed Swashbuckle 5.3.2. in my ASP .NET Web API 5.3.2. project. When trying to enable Swagger using the following code

GlobalConfiguration.Configuration.EnableSwagger(c => { c.OperationFilter<ExamplesOperationFilter>(); }).EnableSwaggerUi();

I get the following MissingMethodException

"An exception of type ‘System.MissingMethodException’ occurred in Swashbuckle.Core.dll but was not handled in user code

Additional information: Method not found: ‘System.Web.Http.Routing.IHttpRoute System.Web.Http.HttpRouteCollectionExtensions.MapHttpRoute(System.Web.Http.HttpRouteCollection, System.String, System.String, System.Object, System.Object, System.Net.Http.HttpMessageHandler)’."

I’m not able to find a solution to this specific problem. Any ideas?

Issue Analytics

State:
Created 7 years ago
Comments:7

Top GitHub Comments

5reactions

ccregocommented, Nov 8, 2018

In order to sort out the issue, was necessary to replace the following binding redirect:

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Net.Http" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
        <bindingRedirect oldVersion="0.0.0.0-4.1.1.2" newVersion="4.2.0.0" />
      </dependentAssembly>
</assemblyBinding>

By the next one:

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Net.Http" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />
      </dependentAssembly>
</assemblyBinding>

1reaction

PoulNielsencommented, Oct 13, 2016

@markus-bergendahl & @markshiffer , Same issue here, Swashbuckle 5.4.0 and AspNet.WebApi 5.2.3. Seems like @markshiffer is right, seems like dll version issue. I fixed it, by added following to my web.config under /configuration/runtime/assemblyBinding/ :

    <dependentAssembly>
        <assemblyIdentity name="System.Web.Http" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
    </dependentAssembly>