Hi Mark,

If you use Reflector (http://www.aisto.com/roeder/dotnet/) to view the
ServiceController's implementation, you will see the WaitForStatus() is
also calling Refresh() while checking the status:

public void WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan
timeout)
{
   if (!Enum.IsDefined(typeof(ServiceControllerStatus), desiredStatus))
   {
       throw new InvalidEnumArgumentException("desiredStatus", (int)
desiredStatus, typeof(ServiceControllerStatus));
   }
   DateTime utcNow = DateTime.UtcNow;
   this.Refresh();
   while (this.Status != desiredStatus)
   {
       if ((DateTime.UtcNow - utcNow) > timeout)
       {
           throw new TimeoutException(Res.GetString("Timeout"));
       }
       Thread.Sleep(250);
       this.Refresh();
   }
}

The Refresh() is a public method.

I understand your concern here is that the exception is expensive; however,
from the timing aspect of this issue, as we're already waiting using sleep,
this is actually might not be a very big issue.

Regards,
Walter Wang (wawang@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.