.net - deployment of owin class library to iis causes 404 -


I am receiving 404 when I place it under IIS sites with a 4.0 intergrate pipeline.

As the console application it works just fine.

My startup file <[Assembly: owin startup (typed (XXX.Owin.Startup)]] namespace XXX.On {Public Class Startup {Private Static Readonly Logger s_logger = LogManager.GetCurrentClassLogger (); Public Zero Configuration (IAppBuilderEpbuilder) {s_logger.Info ("Start"); HttpConfigurationManager httpConfigurationManager = New HttpConfigurationManager (); Http configuration http configuration = http configuration manager Create (); AppBuilder.UseStageMarker (PipelineStage.Authenticate); AppBuilder.Use (async (ctx, next) = & gt; {stopwatch stopwatch = new stopwatch (); stopwatch.start (); wait for further; stopwatch.top (); console.print line ("Requested: { 0} ", stopwatch. Applied milliseconds);}); AppBuilder.Use & LT; CustomHeadersComponent & gt; (); AppBuilder.Use & LT; SecurityComponent & gt; (); AppBuilder.UseWebApi (httpConfiguration); }}

Should I add web.config? Change app.config to web.config? Maybe I can not create an IIS site and set the physical path in the OWin directory?

The problem was that the project was a library and not a web application.


Comments

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -