The MVVm is a great technique for separating the concerns. If we take ASP.Net MVC we can see it is built for using model view controller model. So by default wont allow us to write code behind for the views (We can write inside the cshtml though). But WPF as the technology was not built to use WPF to there is no in-built way to avoid the code behind of views.
If the development team is so technology focused, it doesn't matter as they won't break the rules of MVVm even if there is code behind file. But since companies are offshoring to get cheap labor, enforcing quality is little tricky. As always cheap things comes with less quality. Most of the time people's priority is to get things done in quick way ie by writing everything in code behind instead of going through viewmodel.
The challenge here is how to bring quality with these less skilled labor? One of the way to enforce viewmodel usage is to delete the code behind of views which is nothing but the user controls.
If we just remove the usercontrol.xaml.cs, it will fail as the Initialize method is missing. So how to overcome is?
Add the Initialize method in the view itself. Yes we can write C# code in XAML. So the view user control will look as follows.
<UserControl x:Class="Joymons.MVVmDemo.Views.MainView" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" mc:Ignorable="d" d:DesignHeight="300" d:DesignWidth="300"> <x:Code> <![CDATA[ public MainView() { InitializeComponent(); }]]> </x:Code> <TabControl ItemsSource="{Binding ChildVMs}" SelectedIndex="0"> <TabControl.ItemTemplate> <DataTemplate> <TextBlock Text="{Binding Header}" /> </DataTemplate> </TabControl.ItemTemplate> </TabControl> </UserControl>
I too started using VS 2013. That is why a black background in the code :)
