self-host-webapi

问题 I have developed self-hosted(owin based) web api using console application. In development phase I was running the console application and everything was okay. static void Main(string[] args) { string baseUri = "http://+:8080"; Console.WriteLine("Starting web Server..."); var server = WebApp.Start<Startup>(baseUri); Console.WriteLine("Server running at {0} - press Enter to quit. ", baseUri); Console.ReadLine(); server.Dispose(); } Now I need to deploy my self-hosted web api to run on IIS.So,

问题 I'm looking for a way to dynamically generate web apis and add them at runtime (after selfhosted server has been initialized). Basically the idea would be to: 1. Create a selfhost owin server serving static/already defined controllers (web apis) -> this part is ok At a later time, I want to dynamically generate a new controller and add it somehow to the server so that client can send request to it. -> is there a way to do that? I know I can dynamically build a controller and add it to the

问题 I found great article about client/server implementation via Self Host Web API http://www.asp.net/web-api/overview/older-versions/self-host-a-web-api And I am wondering about the correct authentication method for this model ( Self Host Web API ). Have I use a bearer token authentication ? Is there any other method? Or for example http://www.asp.net/web-api/overview/security/individual-accounts-in-web-api I have following working requirements: C# http client must connect to Self Host Web API

问题 I found great article about client/server implementation via Self Host Web API http://www.asp.net/web-api/overview/older-versions/self-host-a-web-api And I am wondering about the correct authentication method for this model ( Self Host Web API ). Have I use a bearer token authentication ? Is there any other method? Or for example http://www.asp.net/web-api/overview/security/individual-accounts-in-web-api I have following working requirements: C# http client must connect to Self Host Web API