BladWise: I am sorry i didn't understand what you mean by "benefits of code-behind", for cases when you do need to reference view in your view-model, you could make use of attached behavior or make the view-model implement IViewAware. I do not see any reason why you would want to use code-behind .xaml.cs when the same could be done in a neater approach (with attached behavior/IViewAware).
The fact that .xaml.cs is a partial class make it already disfigured, removing .xaml.cs gives you a cleaner structure.
The fact that .xaml.cs is a partial class make it already disfigured, removing .xaml.cs gives you a cleaner structure.