Fabrice's weblog

There's a new OData kid on the block: The data from Proagora.com is now available as OData.

There's a new "link" from Redmond. It's not LINQ this time, but Lync.
Isn't it great to have two names colliding in the Microsoft world?

Given all the activity around databases lately with the NOSQL movement, I decided to give a try to some of the new contenders.

With the release of Microsoft Codename "Dallas" CTP3 and the features announced in the previous post, it became easier to add support for Dallas to Sesame Data Browser.
The new version of Sesame published today allows you to browse Dallas datasets, as demonstrated below.

Sesame Data Browser has just been updated to offer the following features for OData feeds:

When coding applications using design patterns such as MVP (Model-View-Presenter) or MVVM (Model-View-ViewModel), you'll find yourself using data binding and the INotifyPropertyChanged interface all over the place. This means referencing properties quite a lot.

If you need to sign a piece of code - eg. a Silverlight application, like I did with Sesame, an EXE, a DLL, an AIR application, a JAR applet - you need a code signing certificate.

A new version of Sesame has been uploaded. It contains several fixes and adjustments. The fixes concern mainly the filtering row.
This new version also introduces client-side paging, signed bits, and auto-updates.