Timeline for Global.asax Application_Start not hit after upgrade to Sitecore 8.2
Current License: CC BY-SA 4.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2019 at 6:19 | history | edited | Himmat Singh Dulawat | CC BY-SA 4.0 |
beautification
|
| S Feb 9, 2018 at 8:23 | history | edited | Gatogordo | CC BY-SA 3.0 |
added 34 characters in body; edited tags
|
| S Feb 9, 2018 at 8:23 | history | suggested | fettesps |
Added relevant tag
|
|
| Feb 9, 2018 at 3:26 | review | Suggested edits | |||
| S Feb 9, 2018 at 8:23 | |||||
| Dec 4, 2017 at 14:16 | answer | added | Sandeep Pote | timeline score: -2 | |
| Nov 8, 2016 at 16:56 | vote | accept | Nico Grms | ||
| Nov 8, 2016 at 16:56 | vote | accept | Nico Grms | ||
| Nov 8, 2016 at 16:56 | |||||
| Nov 8, 2016 at 16:56 | vote | accept | Nico Grms | ||
| Nov 8, 2016 at 16:56 | |||||
| Nov 8, 2016 at 14:23 | answer | added | Søren Kruse | timeline score: 28 | |
| Nov 8, 2016 at 13:37 | comment | added | Nico Grms | The application is indeed published in debug mode, other breakpoints from the same assembly are hit. I killed the worker process, added Debug.Launch/Break etc.. I'm sure it has nothing to do with the way I try to debug it. The problem is Application_Start is not hit at all. | |
| Nov 8, 2016 at 13:29 | comment | added | Nico Grms | Yes, I did but that didn't work either. | |
| Nov 8, 2016 at 13:25 | answer | added | Chris Auer | timeline score: 26 | |
| Nov 8, 2016 at 13:23 | comment | added | Vinayak Chauhan | Just a thought, Hope you had published in debug mode not in release mode. :) or just get ready, update web.config or reset IIS, refresh the page and attach the worker process. It works actually. Also check Configuration and Platform in Configurations Manager that Configuration is Debug and Platform is Any CPU. | |
| Nov 8, 2016 at 11:03 | comment | added | Dmytro Shevchenko | Have you tried changing the target framework to 4.5.2, as per Mark's suggestion? | |
| Nov 8, 2016 at 11:01 | comment | added | Nico Grms | It's still not executed. I used the exception as a last resort after trying the Debugger.Break() etc. | |
| Nov 8, 2016 at 10:51 | comment | added | Dmytro Shevchenko |
@NicoGeeroms You're probably not restarting the app completely. Detach the debugger, then stop the application pool in IIS, then start it again. See if Application_Start is executed then. Don't use exceptions to check if it's executed (you won't necessarily see them and the app will start anyway). Instead, use Debugger.Break() or write to a file on disk, or something similar.
|
|
| Nov 8, 2016 at 10:43 | history | edited | Nico Grms | CC BY-SA 3.0 |
added 295 characters in body
|
| Nov 8, 2016 at 10:41 | comment | added | Nico Grms | The target framework is set to 4.6 | |
| Nov 8, 2016 at 10:36 | comment | added | Mark Cassidy♦ | Right. Hmm. And you've changed your build target to .NET 4.5.2? | |
| Nov 8, 2016 at 10:36 | comment | added | Nico Grms | Yes, I added a System.Diagnostics.Debugger.Break() which did not work. Then changed the global.asax while the debugger was attached and even threw an exception to make sure it's not hit. | |
| Nov 8, 2016 at 10:33 | comment | added | Mark Cassidy♦ | Are you sure it's not hit? Can easily go wrong, if you're relying on attaching a debugger to see a breakpoint get hit. stackoverflow.com/questions/967813/… | |
| Nov 8, 2016 at 10:30 | review | First posts | |||
| Nov 8, 2016 at 10:34 | |||||
| Nov 8, 2016 at 10:29 | history | asked | Nico Grms | CC BY-SA 3.0 |