AFAIK, the COM object runs in the IIS process space & is locked down by IIs
- try deleting the COM object while IIs is running & you will see :-(
I ended up doing a lot of my debugging using a quick & dirty client whipped
up & Delphi to test the COM object interfaces etc, then using ASP to drive
the tested object.
For lots of detail on what you are trying to do see:
http://www.yasdbooks.com/devaspcomp/bonus/delphi.htm
> -----Original Message-----
> From: Blackie, Nikolai [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 24, 2000 9:19 AM
> To: Multiple recipients of list delphi
> Subject: [DUG]: Delphi 5 and debugging COM objects in IIS
>
>
> Hi I'm new to this list but I have a question for those developing COM
> objects for ASP. I can debug COM in PWS on win98 but I cannot
> do this in
> WinNT4.0 using IIS, I have been told it is something to do with the
> threading model. Has anyone had exp with this, could lend me
> any advice?
>
> Nikolai Blackie
> Business Education On-Line
> School of Business and Economics
>
> --------------------------------------------------------------
> -------------
> New Zealand Delphi Users group - Delphi List -
> [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
