OwinStartup not firing

Question

I had the OwinStartup configuration code working perfectly and then it stopped working   Unfortunately I m not sure exactly what I did to get it to stop working and am having a really hard time figuring it out     To make sure I have the basics covered  I doubled checked to make sure the I have the    assembly OwinStartup typeof WebApplication Startup       attribute assigned properly and made sure that I don t have an appSetting for owin AutomaticAppStartup that is set to false so I made one set to true to be safe as there was nothing there before    lt add key  owin AutomaticAppStartup  value  true    gt    I also tried specifically calling out the appSetting    lt add key  owin appStartup  value  WebApplication Startup    gt    Before it stopped working I upgraded the Microsoft Owin Security NuGet packages to 2 0 2  so I tried reverting them to 2 0 1  that was a pain  but it didn t change anything   I have WebActivator installed on the project and am using that to bootstrap other things but I ve tested that on a fresh WebApplication template and it works there so I don t think that is the culprit   I also tried removing my Startup class and using Visual Studio to add a new one using the OWIN Startup Class type in Add New Item and that isn t getting called either   Next I tried adding a second Startup class since I know it will throw an exception if there is more than one OwinStartup attributes defined  but it isn t throwing any exception there   Not sure what else to try   Any thoughts   Update  Turns out that Resharper removed the reference to Microsoft Owin Host SystemWeb when I used it to remove unused references

User · Accepted Answer

Make sure you have installed Microsoft Owin Host SystemWeb package in the project  This package is needed for startup detection in IIS hosted applications  For more information you can refer to this article

User · Answer

I am not sure if this will still help someone  but I ve done all of the solutions above  and from some other posts  to no avail     What fixed the issue on my end was to put a backslash to the end of RedirectUri  value in the web config  crazy  I know    RedirectUri is a parameter in UseOpenIdConnectAuthentication   So  instead of    lt add key  ida RedirectUri  value  https   www bogussite com home    gt    Do this    lt add key  ida RedirectUri  value  https   www bogussite com home     gt    And updated the Reply URL on the Azure App Settings as well     That somehow made the Startup to run as expected  probably cleared some cache   and the breakpoints are now firing   FYI  I was modelling my code from here  https   github com microsoftgraph aspnet-connect-sample

User · Answer

DEBUGGING TIPS  If debugging does not work try using IIS Express or try the method below for local IIS  Using local IIS   For some reason this method enables debugging of this method    Request a webpage Attach to w3wp exe process Touch the web config file Request a webpage   Extra tip  Maybe doing this will flush a cache    In web config add the optimizeCompilations attribute with a false value   lt compilation debug  true      optimizeCompilations  false    Run site Undo the change in web config

User · Answer

After converting a class library to a Web Application Project  I ran into this and became stubborn  Turned out  in my  csProj file  I had this      lt PropertyGroup Condition      Configuration    Platform       Debug AnyCPU    gt     lt DebugSymbols gt true lt  DebugSymbols gt     lt DebugType gt full lt  DebugType gt     lt Optimize gt false lt  Optimize gt     lt OutputPath gt bin Debug  lt  OutputPath gt     lt DefineConstants gt DEBUG TRACE lt  DefineConstants gt     lt ErrorReport gt prompt lt  ErrorReport gt     lt WarningLevel gt 4 lt  WarningLevel gt   lt  PropertyGroup gt   lt PropertyGroup Condition      Configuration    Platform       Release AnyCPU    gt     lt DebugType gt pdbonly lt  DebugType gt     lt Optimize gt true lt  Optimize gt     lt OutputPath gt bin Release  lt  OutputPath gt     lt DefineConstants gt TRACE lt  DefineConstants gt     lt ErrorReport gt prompt lt  ErrorReport gt     lt WarningLevel gt 4 lt  WarningLevel gt   lt  PropertyGroup gt     thus building the various dll s into a subfolder of the bin-folder  which ifc  won t work   Solution was to change both text-contents for OutputPath to just bin

User · Answer

This worked for me      add authentication mode  None     lt system web gt       lt compilation debug  true  targetFramework  4 6 1    gt       lt httpRuntime targetFramework  4 6 1    gt         lt authentication mode  None    gt  lt  --Use OWIN-- gt     lt  system web gt

User · Answer

Alternative answer to the original problem discussed - Owin  not firing    In my case I spent hours thinking it wasn t firing due to being unable to set a breakpoint in it   When debugging OWIN startup in visual studio   IIS Express - Running  F5  will break on the OWIN startup code IIS - Running  F5  will not break until after OWIN  and global asax  code is loaded   If you attach to W3P exe you will be able to step into it

User · Answer

I messed around with a lot of the suggestions on this post   I had the following but still could not land on a break point  Throwing an exception proved the code was being entered    lt appSettings gt         lt add key  owin AutomaticAppStartup  value  true    gt     lt add key  owin appStartup  value  SSOResource Startup  SSOResource    gt       lt  appSettings gt    Finally out of desperation I looked at project- properties  and then under the WEB section I also checked the NATIVE CODE checkbox  ASP NET should be already checked    That finally fixed it for me   Note   I am using Visual Studio 2017 Professional

User · Answer

In case you have multiple hosts using the same namespace in your solution  be sure to have them on a separate IISExpress port  and delete the  vs folder and restart vs

User · Answer

In my  case this Microsoft Owin Host SystemWeb package is present in the project   But below two tags are not present in web config    lt add key  owin AutomaticAppStartup  value  true    gt   lt add key  owin appStartup  value  namespace className methodName    gt    after adding them it works smoothly

User · Answer

I had a similar issue to this and clearing Temporary ASP NET Files fixed it  Hope this helps someone

User · Answer

For me it was because they are not in the same namespace  After I remove my AppStart from  project Startup AppStart  and let they both Startup cs and Startup Auth cs with  project Startup  namespace  everything was back to work perfectly   I hope it help

User · Answer

First add the OWIN Auth Class and then enable OWIN AutomaticAppStartup key in your web config like  Now it will fire

User · Answer

In my case  my website s output path is changed by somebody  the IIS Express even not load OWIN  and the setup class will not be hit of course   After I set the output path as  bin    it works well

User · Answer

In my case  the IIS application pool was not set to v4  It was v2   Changed the AppPool to v4 and everything was okay

User · Answer

If you are seeing this issue with IIS hosting  but not when F5 debugging  try creating a new application in IIS   This fixed it for me   windows 10  In the end i deleted the  bad  IIS application and re-created an identical one with the same name

User · Answer

In my case  my web config had   lt authorization gt     lt allow users       gt   lt  authorization gt    To force it to fall back to Owin  I needed it to be   lt authorization gt     lt deny users       gt   lt  authorization gt

User · Answer

If you are having trouble debugging the code in the Startup class  I have also had this problem - or I thought I did  The code was firing but I believe it happens before the debugger has attached so you cannot set breakpoints on the code and see what is happening   You can prove this by throwing an exception in the Configuration method of the Startup class

User · Answer

I had same problem when I added Owin to an existing web project  I eventually found the problem was due to the following in the web config file    lt assemblies gt     lt remove assembly       gt     lt add assembly  System Web Mvc    gt     lt add assembly  System Web WebPages    gt            lt  assemblies gt    The remove assembly     was causing the problem  When I remove this line the Owin startup code ran   I eventually change it to the following and it worked perfectly   lt assemblies gt     lt remove assembly       gt     lt add assembly  Microsoft Owin Host SystemWeb    gt     lt add assembly  System Web Mvc    gt     lt add assembly  System Web WebPages    gt     lt add assembly  System Web Helpers    gt       lt  assemblies gt

User · Answer

If you ve upgraded from an older MVC version make sure you don t have     lt add key  owin AutomaticAppStartup  value  false    gt    in your web config  It will suppress calling the startup logic   Instead change it to true     lt add key  owin AutomaticAppStartup  value  true    gt    I realize you already mentioned this but sometimes people  like me  don t read the whole question and just jump to the answers     Somewhere along the line - when I upgraded to MVC 5 this got added and I never saw it until today

User · Answer

I think what some people were trying to get to above is that if you want to programatically make your OWIN server  come to life   you d be calling something like this    using Microsoft Owin Hosting       IDisposable  server   WebApp Start lt StartupMethod gt   http     5000                      Start Accepting HTTP via all interfaces on port 5000   Once you make this call  you will see the call to StartupMethod   fire in the debugger

User · Answer

I had the same problem  Microsoft Owin Host SystemWeb package was installed but during the installation NuGet was not able to add the dll as a reference for some reason  Make sure your project has that reference  If not you can try to reinstall   update-package Microsoft Owin Host SystemWeb -reinstall   I had an error like below on reinstall but somehow it worked      System call failed   Exception from HRESULT  0x80010100    RPC E SYS CALL FAILED

User · Answer

I found the following article to be very helpful   https   weblog west-wind com posts 2015 Apr 29 Adding-minimal-OWIN-Identity-Authentication-to-an-Existing-ASPNET-MVC-Application MinimalCodeSummary  In my case  I had to set the following before Owin authentication would work instead of windows authentication    lt system web gt          lt authentication mode  None    gt      lt system web gt

[asp.net-mvc] OwinStartup not firing

Examples related to asp.net-mvc

Examples related to asp.net-mvc-5

Examples related to owin