Take the 2-minute tour ×  Let's say I have a View that is bound
to ViewModel A which has an observable collection Customers.  An
advantage of this MVVM pattern is that I can also bind the View
to ViewModel B which fills it with different data.  But what if
in my View converter Converters to display my customers, e.g. I
have a "ContractToCustomerConverter" that accepts a Contract and
returns the appropriate Customer to be displayed.  The problem
with this is that the converter exists outside the MVVM pattern
and thus doesn't know that my ViewModel has another source for
customers.    • is there a way for the View to pass the
ViewModel into the Converter so that it participates in the
decoupling that the MVVM pattern provides?   • is there a way
for me to somehow include the Converter in my ViewModel so that
the converter uses the current dependencies which ViewModel has
available?   • or are converters just glorified code-behind and
thus not used in the MVVM pattern, so if you are using MVVM then
you just crea