We have written an ISAPI Extension that sits along side the davex.dll
extension provided with Exchange 2003. Our extension sits above the
davex.dll (in terms of the 'order of implementation') and performs some
additional processing. However, I have now reached a particular situation
where I don't want the davex.dll extension to be called as it overwrites all
the work my extension has done. How can I dynamically prevent IIS from
calling davex.dll?

Thanks for any advice

Alan.

RE: Prevent the next ISAPI Extension being called by adamtuliper

adamtuliper
Wed Jan 05 11:51:07 CST 2005

Would SF_STATUS_REQ_HANDLED_NOTIFICATION work for you?

"Alan" wrote:

> We have written an ISAPI Extension that sits along side the davex.dll
> extension provided with Exchange 2003. Our extension sits above the
> davex.dll (in terms of the 'order of implementation') and performs some
> additional processing. However, I have now reached a particular situation
> where I don't want the davex.dll extension to be called as it overwrites all
> the work my extension has done. How can I dynamically prevent IIS from
> calling davex.dll?
>
> Thanks for any advice
>
> Alan.
>
>
>

RE: Prevent the next ISAPI Extension being called by adamtuliper

adamtuliper
Wed Jan 05 11:57:12 CST 2005

You did say extension, my apoligies, my mind is in isapi filter mode : )

"Alan" wrote:

> We have written an ISAPI Extension that sits along side the davex.dll
> extension provided with Exchange 2003. Our extension sits above the
> davex.dll (in terms of the 'order of implementation') and performs some
> additional processing. However, I have now reached a particular situation
> where I don't want the davex.dll extension to be called as it overwrites all
> the work my extension has done. How can I dynamically prevent IIS from
> calling davex.dll?
>
> Thanks for any advice
>
> Alan.
>
>
>