WHat context are you talking about? A Web Service should be completely stateless and if you need state you should use the ASP Session object for that (can't do that with the ISAPI listener).

You can hook the Session through the IObjectContext interface for the COM component.

+++ Rick ---

>Yesterday, it was brought an interesting information to me, based on Randy Brown's class to be used as a project hook in order to compile our Web Service as COM+ which would fit inside MTS.
>
>That class requires the project definition to be multi-threaded. So, we applied the change in our project definition to be multi-threaded. The Web Service is now created under MTS and updated automatically at build time - thanks to Randy's class for that. However, we discovered that using the Web Service as multi-threaded has some impact, as when we use such an approach, if the Web Service uses the default ASP listener file, we loose our context. So, in order to bypass that, we have to use a custom ASP listener file which will create a context prior to calling the Web Service.
>
>So, this means, in order to remain as standard as possible, which means to only compile our DLL and use the default ASP listener file generated by the WSDL generator, we have to define our Web Service to be single-threaded. As the Web Service is now again single-threaded, we have to use the old method which is IISRESET /RESTART. This method is longer and shuts down the IIS services while it is being done.
>
>Another approach would be to define the Web Service is a specific virtual directory, define it as Isolated and use the Unload option from MMC everytime we have to compile. By that, we only shut down the components from that directory.
>
>Comments?