Yeah, that's fine... but sometimes, I've found that sometimes IIS just wont let go and you may NEED to stop it completely, clear what you want, then restart... Especially if the IIS has a request stuck in its queue... You stop the COM+ and one request is released with anothe right behind it thus re-opening the dll. Just an FYI.



>Thanks Don
>
>At the moment I am trying out COM+. reading Craig Bernstons article
>
>http://www.craigberntson.com/blog/2006/08/new-comvfp-article-posted.asp
>
>
>Nick
>
>>Try getting to a DOS window, then
>>
>>NET STOP w3svc
>>
>>Then, replace your dll, then
>>
>>NET START w3svc
>>
>>Doing the IIS Restart does the stop / start but no delay to allow you to do your swap-out.
>>
>>
>>>Hi
>>>
>>>I have a foxpro dll running via interop in a .net web service. Previously I have been able to replace this dll by running iisreset and then putting in a new copy.
>>>
>>>I can't run iisreset any more because other parts of the web site need to prrserve their session state so often the dll is marked as in use and I can't replace it. Does anyone have any suggestions for the best way to manage the replacement of a fox dll in a web service.
>>>
>>>
>>>Thanks
>>>
>>>Nick Mason