.NET RIA Services

Flex\Flash\AIR vs Silverlight: conquering the land of RIA

We are living in interesting times. Rich internet applications with next generation user interface are in increasing demand, and so the great RIA war is raging on, with Adobe and Microsoft as major players struggling for market prevalence. The competition is good, as it forces both companies to deliver new versions of their products more rapidly, and with more and more impressive sets of features. The competition is bad, as it forces companies to haste, sometimes delivering features in raw and incomplete form, and focusing more on new features than on polishing the existing ones. And the war makes the situation changing so fast that sometimes it's hard to understand what's going on at this very moment. That is why it's always good to write yet another article trying compare both technologies: yes, there are a number of other articles doing the same job (like this and this, for example), but they are becoming outdated very rapidly, and sometimes miss one or another important topic.

.NET RIA Services: intermediate model validation.

I'm not the first person firmly believing that validation should be mostly entity-based, not UI control-based. It's the object who must tell the system what kind of values should its field accept, user interface should only display this info. Microsoft Enterprise Library Validation Block was a serious step in the right direction, but uniform handling of data-based validation exceptions in user interface required quite a bit of custom coding there - just to make your UI know that the data was invalid.

Now, with validation attributes in System.ComponentModel.DataAnnotations namespace uniformly supported both in Silverlight (through .NET RIA Services) and in ASP.NET Dynamic Data, Microsoft makes even more serious step in supporting entity-based validation.

Syndicate content