title: Is this called adapter? + adapter vs decorator
body: <p>I have 2 projects: A and B that should interactwith each other.   </p>
  
  <ol>
  <li><p>Project A introduce interface names ISpecialTask and Project B should implement it.   </p></li>
  <li><p>Projet B has an entity named TaskWithListOfProperties that cannot implement ISpecialTask because it has different structure of properties (in addition, all the system knows how to work with TaskWithListOfProperties and I don't want to change its structure). </p></li>
  </ol>
  
  <p>So I decided to create a class named SpecialTaskFromListOfProperties that implements ISpecialTask and uses TaskWithListOfProperties instance in order to use it for the interaction between the projects.</p>
  
  <pre><code>interface ISpecialTask {
      long Id{get;}
      long WorkerId{get;}
      long VehicleId{get;}
      long CustomerId{get;}
  }
  
  class TaskWithListOfProperties {
      IDictionary&lt;string, long&gt; Properties {get;
  }
  
  class SpecialTaskFromListOfProperties : ISpecialTask  {
      public SpecialTaskFromListOfProperties(TaskWithListOfProperties  ins) {
          ...
          ...
      }
      public long Id { get{ ... } }
      public long WorkerId { get{ ... } }
      public long VehicleId { get{ ... } }
      public long CustomerId { get{ ... } }
  }
  </code></pre>
  
  <p>Is SpecialTaskFromListOfProperties actually the Adapter pattern?<br>
  What is the difference between the adapter pattern and decorator pattern?</p>