标签:external doc tree tar containe through create tag member
https://github.com/autofac/Examples/tree/master/src/WebApiExample.OwinSelfHost
https://github.com/autofac/Examples/blob/master/src/WebApiExample.OwinSelfHost/Startup.cs
https://autofaccn.readthedocs.io/en/latest/integration/owin.html
OWIN (Open Web Interface for .NET) is a simpler model for composing web-based applications without tying the application to the web server. To do this, a concept of “middleware” is used to create a pipeline through which requests travel.
Due to the differences in the way OWIN handles the application pipeline (detecting when a request starts/ends, etc.) integrating Autofac into an OWIN application is slightly different than the way it gets integrated into more “standard” ASP.NET apps. You can read about OWIN and how it works on this overview.
The important thing to remember is that order of OWIN middleware registration matters. Middleware gets processed in order of registration, like a chain, so you need to register foundational things (like Autofac middleware) first.
To take advantage of Autofac in your OWIN pipeline:
Autofac.Owin
package from NuGet.
https://autofaccn.readthedocs.io/en/latest/integration/webapi.html#owin-integration
If you are using Web API as part of an OWIN application, you need to:
A common error in OWIN integration is use of the GlobalConfiguration.Configuration
.
In OWIN you create the configuration from scratch.
You should not reference GlobalConfiguration.Configuration
anywhere when using the OWIN integration.
integration asp.net web api with autofac and owin
标签:external doc tree tar containe through create tag member
原文地址:https://www.cnblogs.com/chucklu/p/10334224.html