DotNet Snippets^1.0

If you're using silverlight to develop apps, you "should" follow the MVVM pattern, ie Model-View ViewModel. It is basically the pattern for databinding between your data Model and the View. Remember, it is just a recommended pattern, and everything else are helpers. It is OK to have code in your code-behind, but this should be kept to a minimal, and ideally most stuff of your business logic is abstracted out to the model.

Here is a great link to get started and learn more: MVVM Light Toolkit
I very much recommend watching his video from MIX 2010.

• Comments / Show

Lets say you want to change the Visual state of a control, for example button1. In the codebehind you would go:

VisualStateManager.GoToState(button1, "MouseOver", true);

Notes: You can only set the visual state of a control that is of control type, ie a Button has visual states but a Grid or TextBlock does not. I know that is lame...

• Comments / Show

So, lets say that you created a silverlight button control and you are overriding the default template with your own defined template. Now, let's say you need to databind, say, the TextBlock text property on an event, but you cannot acces the TextBlock directly because it is within a template. Solution: Simply set the TextBlock Text property to:

{Binding ObjectPropertyName}

and then in the code behind in your event that will bind the data, go:

Button.DataContext = ObjectWithDefinedProperties;

• Comments / Show