Q: Does Swagger.net works with higher .Net frameworks than 4.0 I have developed a WebAPI and trying to document it using Swagger.Net. My .Net framework version is 4.5.1 where as Swagger.Net appears to be written in .Net 4.0. So its always ending up with System.Web.Http version incompatibility error (located assembly manifest definition does not match the assembly reference). Solution compiles successfully but when it opens in the browser, it errors.
Also I have tried to recompile Swagger.net source code in VS 2013 and .Net framework 4.5 but even than it ends up while requiring System.Web.Http 4.0.0.

A: @theGeekster:  FYI, you can now use WebAPI 2.x with this fork:
https://github.com/Gcastelo/Swagger.Net
The original swagger.net project looks dead.
Enjoy!

A: I do not think Swagger has been updated to be used along with latest versions 5.0 and 5.1 of ASP.NET Web API. Your issue could be solved by binding redirects, but I can imagine Swagger to fail with latest versions of Web API as things have changed a lot since Swagger's last release..try adding the following to your web.config.
  <system.webServer>
    <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="System.Web.Http" publicKeyToken="31bf3856ad364e35" />
          <bindingRedirect oldVersion="1.0.0.0-5.0.0.0" newVersion="5.0.0.0" />
        </dependentAssembly>


A: I have ended up with conclusion that using Swagger.Net, we can't use Attribute Routing (or other WebaPI2 features like native CORS support etc.)
