title: What exactly are "WPF services"?
body: <p>Someone told me in an <a href="https://stackoverflow.com/questions/921775/when-does-it-make-sense-to-abandon-mvvm">answer to a stackoverflow question</a> that the "two big guns" for the MVVM pattern are 1) <strong>attached behaviors</strong> and 2) <strong>services</strong>. I assume he means "<strong>WPF services</strong>" a phrase which I found used in the following ways:</p>
  
  <blockquote>
    <p><em>PresentationFoundation.dll defines the WPF controls types, animation and
    multimedia support, data binding
    support, and other <strong>WPF services</strong>.</em></p>
    
    <p><em>Many of these <strong>WPF services</strong> ( de-coupled eventing, rich databinding,
    styling, resources, etc.) are software
    development best practices that
    converge in a single, declarative UI
    stack.</em></p>
    
    <p><em>You will understand the motivation behind WPF, learn the syntax of XAML,
    examine the core programming model, and survey several <strong>WPF services</strong>.</em></p>
  </blockquote>
  
  <p>None of the WPF books I have even mention "WPF services" as such, so is this just a word that means "<strong>WPF features</strong>" such as decoupled eventing, rich databinding, styling, etc. or is there something else behind the term "WPF Services"?</p>