| | [Bridge](/StructuralPatterns/Bridge) |

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Threading.Tasks;

namespace StructuralPatterns.Bridge

public class BasicRemote : IRemote

{

public void PowerOn()

{

throw new NotImplementedException();

}

public void PowerOff()

{

throw new NotImplementedException();

}

public void VolumeUp()

{

throw new NotImplementedException();

}

public void VolumeDown()

{

throw new NotImplementedException();

}

}

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Threading.Tasks;

namespace StructuralPatterns.Bridge

public interface IDevice

{

void PowerOn();

void PowerOff();

int GetVolumen();

void SetVolume();

}

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Threading.Tasks;

namespace StructuralPatterns.Bridge

// Abstraction

public interface IRemote

{

void PowerOn();

void PowerOff();

void VolumeUp();

void VolumeDown();

}

* Decouples an implementation so that it is not bound permanently to an interface.

* Abstraction and implementation can be extended independently.

* Changes to the concrete abstraction classes don't affect the client.

* Allows building platform independent code

* Hides the implementation details from client

* Increases overall code complexity by creating multiple additional classes.

* Useful in graphic and windowing systems that need to run over multiple platforms

* Useful any time you need to vary an interface and an implementation in different ways

// TODO

* **Adapter** makes the unrelated classes work together. Adapter makes things work after they're designed; Bridge is designed beforehand to let the abstraction and implmentation vary independently. *[GoF, p219]*