Someone told me in an answer to a stackoverflow question that the “two big guns” for the MVVM pattern are 1) attached behaviors and 2) services. I assume he means “WPF services” a phrase which I found used in the following ways:
PresentationFoundation.dll defines the WPF controls types, animation and
multimedia support, data binding
support, and other WPF services.Many of these WPF services ( de-coupled eventing, rich databinding,
styling, resources, etc.) are software
development best practices that
converge in a single, declarative UI
stack.You will understand the motivation behind WPF, learn the syntax of XAML,
examine the core programming model, and survey several WPF services.
None of the WPF books I have even mention “WPF services” as such, so is this just a word that means “WPF features” such as decoupled eventing, rich databinding, styling, etc. or is there something else behind the term “WPF Services”?
He’s not talking about WPF services, but application services. That is, abstracting some portion of functionality into an independent service that multiple VMs can consume.