|
<< Click to Display Table of Contents >> Navigation: Telegram > 2021 > 06 > 03 > Telegram_2021-06-03T20 |
2021-06-03T20:02:53
I am not having any luck getting the ISAPI dll to load locally so I am not able to debug it that way. Is there any other way I can get you the info for the runparams property?
2021-06-03T20:22:10
You can log it to a file
2021-06-03T20:23:16
declare IW.Common.SysTools in your unit.
and use funciton LogFileAppend('your text here');
2021-06-03T20:23:21
IW will log it to the application log file
2021-06-03T20:23:37
debugging ISAPI is not hard
2021-06-03T20:24:07
type: link https://stackoverflow.com/questions/44190866/how-to-debug-an-isapi-extension-using-the-delphi-debugger/44191683
2021-06-03T20:24:16
this is my answer on SO
2021-06-03T20:25:29
However, there are 2 different things here.
ASPX is one thing and ISAPI is a different thing. They both run under IIS but they are different application types
2021-06-03T20:28:16
I was following that article on debug the ISAPI dll but can't even get it running under IIS locally. I will work on this but will try to output the runparam info to application log for right now
2021-06-03T20:40:44
I am doing the following in my custom content handler unit: LogFileAppend(aSession.RunParams.text);
2021-06-03T20:41:15
When running it as ASPX I just get a date/time entry in the event log: 6/3/2021 8:38:33 PM
2021-06-03T20:41:45
When I run it as a GUI I get the following: 6/3/2021 8:35:08 PM gid=9D8AA17B-15FD-4033-A36A-393787023BF2
2021-06-03T20:48:14
Can you confirm that you are running as ASPX module, not ISAPI?
2021-06-03T20:48:26
because you've been using both terminologies but they are not the same
2021-06-03T20:48:49
Sorry for the confusion. All the IW apps I run, run as ASPX