tag:blogger.com,1999:blog-5819005.post5935654839903328490..comments2024-03-16T02:17:55.433-07:00Comments on Programming and politics: Silverlight StocksAnonymoushttp://www.blogger.com/profile/08698131967747444207noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5819005.post-49498873311608394152008-03-16T08:44:00.000-07:002008-03-16T08:44:00.000-07:00Yes, .NET generally has straightforward databindin...Yes, .NET generally has straightforward databinding in many places, so Silverlight should be no different. For the stocks app, if you didn't use explicit binding to the mx:HttpService, you could create a data object and just annotate it with [Bindable]. This tells the framework to enhance the class with event publishers, so updates to controls happen automatically. I suppose the Silverlight way would be similar?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5819005.post-5756771958035827302008-03-16T06:31:00.000-07:002008-03-16T06:31:00.000-07:00I've been at Robertjan's presentation on silverlig...I've been at Robertjan's presentation on silverlight 2.0 for developers (http://www.robertjantuit.nl/) and he demoed databinding from a WCF to a Silverlight control and it was pretty straightforward. I can't remember the details, but I'm sure you can figure it out. I am now learning a bit of actionscript, but I find Silverlight easier since I already have some background on .NET.Anonymousnoreply@blogger.com