Anatoly Lubarsky

There is a common problem with smart client applications that they need to implement monitoring network connectivity. Common scenario - if the computer is connected - send data to the server, otherwise - serialize data to disk, then wait for network connectivity becomes available and when the network is available - send serialized data to the server in the background.

.NET 2.0 introduced System.Net.NetworkInformation with NetworkAvailabilityChanged event, so there is no need to reinvent network monitor behavior by hand any more :)

Use the right namespace :)

using System.Net.NetworkInformation;

Now it is possible to check connectivity on demand...

bool connected = NetworkInterface.GetIsNetworkAvailable();

Or subscribe to event in some place....

NetworkChange.NetworkAvailabilityChanged += OnAvaiabilityChanged;

Implement like so:

private void OnAvaiabilityChanged(object sender, 
    NetworkAvailabilityEventArgs args)
{
    this.UpdateStatus(args.IsAvailable);
}

private void UpdateStatus(bool connected)
{
    if (connected)
    {
        ...
    }
    else
    {
        ...
    }
}

Enjoy :)

Related Posts:

• ArrayList as Array of Object Arrays
• ExecuteReader, ExecuteNonQuery, ExecuteScalar ... When to use What ?
• How to Serialize One-to-Many
• Use RSACryptoServiceProvider Instead of RSA for Asymmetric Encryption
• Enterprise Library sucks big time
• .NET Framework 3.0 - Release Candidate is available
• Setup Bootstrapper for .NET Application
• Genghis Library: AniForm and the rest
• .Net 2.0: String.IsNullOrEmpty causes runtime exception
• Enterprise Library 2 Logging: Rolling file trace listener