Ping until a machine responds

It appears that the virtual machine manager in HyperV (VMM) reports the VM as running though the OS may not yet be fully loaded. We need to wait until the OS is responsive before continuing VM configuration. This observed behavior is more empirical than scientific and requires investigation, but a stop-gap solution is to wait until the VMM reports that the VM is running and then wait for the machine to respond to pings. This code does the second part.

using System.Net.NetworkInformation;

public class Test
{
	public static bool Ping(string name, int waitForPostivePingTimeout = 0) 
	{
		if(string.IsNullOrEmpty(name)) return false;
		if(waitForPostivePingTimeout < 0) waitForPostivePingTimeout = 0;
		var timeout = DateTime.Now.AddMilliseconds(waitForPostivePingTimeout);
		
		do
		{
			try
			{
				Ping p = new Ping();
				PingReply reply = p.Send(name, 2000);
				if(reply.Status == IPStatus.Success) return true;
			}
			catch{}
		} while(DateTime.Now < timeout);
		return false;
	}
}

using System.Net.NetworkInformation;

public class Test

{

public static bool Ping(string name, int waitForPostivePingTimeout = 0)

{

if(string.IsNullOrEmpty(name)) return false;

if(waitForPostivePingTimeout < 0) waitForPostivePingTimeout = 0;

var timeout = DateTime.Now.AddMilliseconds(waitForPostivePingTimeout);

{

try

{

Ping p = new Ping();

PingReply reply = p.Send(name, 2000);

if(reply.Status == IPStatus.Success) return true;

}

catch{}

} while(DateTime.Now < timeout);

return false;

}