tag:blogger.com,1999:blog-34300632.post5174919320673518460..comments2008-11-23T00:19:42.816+05:00Alex Yakuninhttps://profiles.google.com/106345489701934677304noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-34300632.post-55887115988883030812008-11-23T00:19:00.000+05:002008-11-23T00:19:00.000+05:00We don't have such near-time plans, but we're going to support Silverlight. Related works must start ~ in January, and frankly speaking, we hope this won't be too complex. We have quite loosely coupled architecture now, so mainly we should provide slower, but Silverlight-compatible versions of just several parts, such as Tuples, AssociateProvider and a set of delegate related helpers.<BR/><BR/>During this phase we'll also try to produce a version compatible with Mono - Mono seems more compatible with .NET 2.0 in comparison to Silverlight. I suspect the primary source of problems here can be LINQ and expressions support in it, although I didn't check its state in Mono for several months.Alex Yakuninhttp://www.blogger.com/profile/13800929290476802273noreply@blogger.comtag:blogger.com,1999:blog-34300632.post-69686086017990558682008-11-22T13:58:00.000+05:002008-11-22T13:58:00.000+05:00Do you planing DO 4.0 for mono? May be without some functionality like WPF events.Vladimirhttp://www.blogger.com/profile/01731169024681618550noreply@blogger.comtag:blogger.com,1999:blog-34300632.post-9045449923662185632008-11-17T23:39:00.000+05:002008-11-17T23:39:00.000+05:00Unfortunately we couldn't publish the update on Sunday, as well as today - there is a single tricky problem we should resolve now: WPF sample doesn't work because of a problem with aspect injecting a protected constructor (it allows DO to create entity instance fast). Invocation of this constructor leads to an exception, although its IL seems correct. Strange, but we don't face the same problem with tests.<BR/><BR/>We hope to fix it tomorrow and publish the update.Alex Yakuninhttp://www.blogger.com/profile/13800929290476802273noreply@blogger.com