Solution for boring thingsIn WPF development is a common thing you add aCustomControl and after add a Dictionary and "link" both with a common name like that: MyCustomControl.cs MyCustomControl.xaml.cs Visual Studio will think that these two files aren't independents. This is very good because avoid the need to view all the files and become very organized like ASP.NET does withaspx, aspx.cs and aspx.designer.cs files. What about this item template?This item template adds a CustomControl.xaml and aCustomControl.xaml.cs. After that creates the basic logic of a CustomControl in thexaml file. You can easily try to change from design to code and vice-versa with Visual Studio shortcuts and you don't need do create both files in a separate step. |