Url: http://wilderminds.blob.core.windows.net/downloads/takingmypicture...

As many of you don't know, I was previously known as "The ADO Guy" so of course my first jump into the new Silverlight 4 bits was to play with the new Data Binding changes. The improvements aren't dramatic but they do fill several key holes that existed in the earlier versions.  Let's take these changes one at a time.

Url: http://timheuer.com/blog/archive/2009/11/18/wha...

Url: http://silverlight-tour.com

Url: http://www.dotnetrocks.com/default.aspx?showNum...

Url: http://wilderminds.blob.core.windows.net/downloads/CollectionViewF...

Url: http://www.cloudcasts.net/ViewWebcast.aspx?webc...

Url: http://www.dotnetrocks.com/default.aspx?ShowNum...

Url: http://niagara.codeplex.com

Url: http://slextensions.codeplex.com

Url: http://www.microsoft.com/europe/teched/

Url: https://mvp.support.microsoft.com/profile/Shawn...

Url: http://agilitrain.com/workshop/info/Silverlight...

If you're a regular reader of my blog, you'll probably remember my pithy blog post where I stated that "It all depends..." to the question "Which Data Access Should I Use for Silverlight 3?"  The reality is that much like the similar question I am confronted with at user groups for the past decade ("What data access should I use in my .NET app?"). The reasons for picking a strategy are wide and varied so I will not try to analyze all possible outcomes, but I think the different strategies need to be explained better.

As RIA Services is plodding towards a release, many people are looking at it to help them with validation of data in Silverlight. Using this validation in Silverlight 3 is pretty straightforward but there are some caveats.  I want to show you under the covers so you understand what is happening. In this first part of the series, let's look at what it means to use validation from the outside.

Url: http://niagara.codeplex.com

Url: http://niagara.codeplex.com

Url: https://agilitrain.com/workshop/info/Silverligh...

Today I was working with a client and ran into a problem I didn't expect. This particular problem had to do with Silverlight consuming a WCF Service. Sometimes WCF causes me to spew four letter words. There is a class of WCF problems that cause this: connection rejection. WCF has been designed to prevent common DDoS and other attacks that could cause servers to fail or at least not serve honest requests. To this end the default size of a request is quite small. In fact, its usually 64K in size. This size is fine for most every request but occassionally when a client wants to send a collection of things to the server this size is too small. But we'll get to that in a minute. First, some background...

If you've been following my blog, you should know that I am keeping a pretty close watch on ADO.NET Data Services. The team recently released a second CTP of the new version with some interesting features. This CTP has some pretty compelling additions, but I am going ot focus on one in particular.

Url: http://www.silverlightdata.com