C#

mirano wrote:

The easiest way is to add a reference to the server, but doing that and in a short time the server implementation gets bloated with too many assemblies.

public interface IClient
{
    event EventHandler ClientChanged;
}

public class Server
{
    public void Connect(IClient client)
    {
        client.ClientChanged += new EventHandler(HandleClientChangedEvent);
    }

    public void Disconnect(IClient client)
    {
        client.ClientChanged -= new EventHandler(HandleClientChangedEvent);
    }

    private void HandleClientChangedEvent(object sender, EventArgs e)
    {
        // Do something here in response to the client's event.
    }
}

public class SomeClient
{
    public SomeClient(Server s)
    {
        s.Connect(this);
    }

    // ...
}

Giles wrote:

Seems the only reasonable way of playing a sounds - such as a .wav is to go back down to Win32?

Giles wrote:

I guessed there would be something like that. Problem is .NET 1.1.

I've currently got a third party lib, and it does not like 2.0, as its a wrapper for a C++ class, linked to the 7.1 C++ runtime.

Leslie Sanford wrote:

If you need some help in this area, let us know. I've had some experience wrapping the MIDI API, so I may be able to give you some pointers on wrapping the sndPlaySound function, or probably someone here at Code Project has already done it.

glocklt4 wrote:

Does anyone else experience this?

AllowDrop<code> property set to true? In this case, Windows Forms would specify the NO_CURSOR because you can't drop there. <br />
<br />
"we must lose precision to make significant statements about complex systems."<br />
-deKorvin on uncertainty

[DllImport("winmm.dll", SetLastError=true)]
static extern bool PlaySound(string pszSound, System.UIntPtr hmod, uint fdwSound);