The automatic bundling of WebApi has made it harder to be able to use MVC with an alternative Open Source Web or Service framework as we now have to include offline manual instructions in order to disable WebApi and allow other frameworks to work as they did before it was bundled.
It would be nice if you could support a directive that framework authors could add to entirely disable WebApi automatically when a user installs an alternative OSS framework via NuGet.
You could copy the same strategy that was used to disable ASP.NET webpages, i.e by adding the appSetting:
http://stackoverflow.com/a/6487815/85785
<add key="webpages:Enabled" value="false" />
Which could be added via Web Transforms (via NuGet).
So for WebApi it could look like:
<add key="webapi:Enabled" value="false" />
For those that don't like Web.config, a static config property to disable it in code would also be appreciated.
Comments: That's not a solution. IMO, the solution is to provide an ASP.NET MVC project template which contains no ASP.NET Web API stuff.
It would be nice if you could support a directive that framework authors could add to entirely disable WebApi automatically when a user installs an alternative OSS framework via NuGet.
You could copy the same strategy that was used to disable ASP.NET webpages, i.e by adding the appSetting:
http://stackoverflow.com/a/6487815/85785
<add key="webpages:Enabled" value="false" />
Which could be added via Web Transforms (via NuGet).
So for WebApi it could look like:
<add key="webapi:Enabled" value="false" />
For those that don't like Web.config, a static config property to disable it in code would also be appreciated.
Comments: That's not a solution. IMO, the solution is to provide an ASP.NET MVC project template which contains no ASP.NET Web API stuff.