Last post Mar 28, 2019 08:57 AM by PatriceSc
Mar 25, 2019 03:49 PM|Sri@2019|LINK
We have a application that runs on asp.net classic pipeline mode (IIS 10) and we are having issues using intellitrace to capture the logs. We are using default trace config. I have tried this with a sample application as well. The tracing works fine if
the app pool is set "integrated" when I change it to "Classic" it stops capturing the logs.
I'm using standalone intellitrace that was shipped with VS2017. I'm wondering if there are any setting that I need to change to capture the logs.
Mar 26, 2019 05:59 AM|Wei Zhang|LINK
According to our descrpition,classic mode is a mode where IIS only works with ISAPI extensions and ISAPI filters directly. In fact, in this mode, ASP.NET is just an ISAPI extension (aspnet_isapi.dll) and an ISAPI filter (aspnet_filter.dll). IIS just
treats ASP.NET as an external plugin implemented in ISAPI and works with it like a black box (and only when it's needs to give out the request to ASP.NET). Else, Intellitrace enables application debugging using a historical execution log.If you use classic
mode of IIS ,it may not provide managed modules to deal with these operation.
For more details , you could send this case to msdn forums.Here is the link, I hope it could help you.
Mar 28, 2019 01:28 AM|Sri@2019|LINK
Thanks for the information and I do understand in classic mode asp.net is an extension and I did post it in msdn forums and they requested me to post it here.
Mar 28, 2019 08:57 AM|PatriceSc|LINK
According to http://continuouslyintegrating.blogspot.com/2011/05/windows-7-sp1-iis-and-intellitrace.html it seems possible by changing a "setProfileEnvironment"