Caliburn.Micro has features to allow you bind methods to actions with parameters. Check out the Action Parameters section of the documentation. Part of this set of features includes “special values” such as $eventArgs or $dataContext, these allow an easy to access information contextual to the action. How can we use them?
In most MVVM style frameworks we’re used of seeing pairs of views and view models, RepositoryView and RepositoryViewModel for instance. We may sometimes have view models without views (such as GroupViewModel) but how do we deal with instances when we want views for types that aren’t view models?
The string resources most commonly used for localisation were before WinRT stored in .resx files. These had a handy feature that they also generated a strongly typed accessor class for when you needed to refer to resources in code. In WinRT however we use .resw files and for whatever reason there isn’t a associated code generator. So how do we get strongly typed access to our string resources?
These days I’m doing my development work over a number of machines both here at home and at Marker Metro. I’m a big fan of having the development environment being as similar as possible across all the machines (including things like keyboard and mouse where possible). One thing I really want to keep in sync is my Powershell profile across all these machines.
Quick public service announcement, Caliburn Micro, one of the best (IMHO) MVVM frameworks for Xaml applications has moved from Codeplex to GitHub.