Samples

1. Introduction

Beta versions of Silverlight 4 and .NET Framework 4 are already a fact. There are just a few weeks until the official releases. One of the coolest features which will be part of .NET Framework 4 and also will be available for Silverlight applications is the RX Framework. The arising interest around the RX Framework made me roll up my sleeves and start playing around this.
So the first step was to answer several important questions such as: “what is Linq to Events?”, “what is RX Framework?”, and “what is Reactive Programming?” And generally what lies behind these sound terms? Linq to events or RX Framework (also known as Reactive Extensions for .NET Framework) is one and the same designation for a library for composing asynchronous and event-based programs using observable collections.

Introduction

As I promised earlier on Silverlight Show, this screencast series will show how to create the showcase application shown on www.response.hu (you may want to read the interview to get some background information on the project). The screencast series shows a real life example of how designers can add value to a project, and how a developer can support this effort by creating small, reusable behaviors that allow the designer to tweak things to shape the end result to be exactly as he wanted it.

Introduction

In this article we’ll look at building a spider, which can load web pages and extract links. It will then allow the user to select which links it wants to retrieve, which adds more links to the list. It will look something like this:

Building it will involve using a two-way DOM Bridge to interact with JQuery and building some parsing mechanism to use on the HTML we retrieve.

Introduction

Last month I wrote about how we could take some of the new features of Silverlight 4, Webcam control,  and create a simple application that lets you store captured webcam photos to isolated storage and your file system.

In this article we will take this proof of concept and demonstrate how through the use of commanding and binding we can virtually eliminate all code behind and implement to a strong MVVM architectural pattern.

Getting Started

I think few would argue with the value of a strong separation of concerns within the design of an application.

In the previous part of this article I introduced a custom Form control I made for some real world projects. I've briefly explained the reasons why I choose to not use the Silverlight Toolkit's DataForm, just before to show how to build this control, and I've also detailed what I like of the DataForm and what I should retain in my Form control.  One of this features is the validation of the input and it is what I'm about to describe in the second part.

Download Source Code

The databinding in Silverlight directly supports the validation through a couple of attributes, that let the developer specify if the markup extension has to notify validation exceptions to the control binded to a property so it can show the errors to the user.

Working with DataForm I found difficult to use it in many scenarios due to its design. So I've created a control where I do not generate fields but I handle automatic validation and cancel/commit commands enabling also the usage of the control in mvvm scenarios. This is a good starting point to understand about Validation, BindingExpressions and traversing the visual tree.

-----

The first time I've met the DataForm control - it was some days after its beta release in the Silverlight Toolkit - I was really astounded from its power. It is capable of many wonders: it generates fields detecting the properties of the binded item, it automatically validates the input values using a bunch of attributes in a way similar to ASP.NET Dynamic Data, it manages the workflow passing through Edit, ReadOnly and Insert state, and these are only a small subset of the features it exposes.

Read part 2 of this article series called: A simplified DataForm replacement - Part 2 Adding validation support

Introduction

Some years ago (pre-silverlight times) a client ask me for a weird requirement…he wanted to drag files from his local explorer and drop them on their ASP .net grid application without using any ActiveX help… I thought, umm… is that possible?

With the advent of Silverlight 2 we got the same request again, … we knew this time it was not a technology limitation, it was a sandbox security limitation, how does the Ms chaps can offer this feature without exposing a security hole? Well it seems that they have managed to “open the box” for this feature in Version 4 on a secure and very easy to use way.

1. Introduction

This is the second article of my series about Silverlight web services tricks. At first time I planned to write only about WCF and that is why I called my article series “Deep dive into WCF”, but with my last experience I decided to move away from mainstream and offer some new unusual stuff. That is why I have generalized name of this series to “Deep dive into Silverlight services”.

In this article I’m going to show how you can build a super fast REST web services using ASP.NET MVC and Google Protocol Buffers library.

Whenever a new version of Silverlight is released, I start examining its features from two perspectives: how would my current (and planned) LOB applications benefit from using these new features, and what cool new things can I build to entertain my children.

This article will guide you through the process of creating a doodling application (you know, for kids ;)), while covering some of the most visible (or not) new features, coming with Silverlight 4. But this is not just about new features, it’s about how they are prepared and served.