User (Old forums)MemberOctober 7, 2007 at 12:07 pmPost count: 23064
Imported from legacy forums. Posted by jmcfet (had 474 views)Odi [Xceed]SpectatorOctober 9, 2007 at 12:07 pmPost count: 426
Thanks for the praise on Xceed DataGrid for WPF.
Your main question seems to be about WPF vs. Silverlight. These are two fundamentally different beasts, though they are more related cosmetically than anything else. It is an interesting subject that has yet to reveal all its implications…
WPF is all about creating the richest possible Windows desktop application experiences, though thanks to Click-Once and XBAP, you can make deployment and maintenance a whole lot more painless than usual. It has also been out for nearly a year and is also about to receive its first major update with .NET 3.5, so it is not a v1 anymore. The keywords for WPF are Windows, Richest and Now.
Don’t let Silverlight v1.0 enter the equation, it is only a spearhead, a way to get an initial Silverlight plug-in installed on as many systems as possible, with video as the bait. Silverlight updates to v.Next automatically. Silverlight v1.1, with its cross-platform, cross-browser version of the .NET framework, C#, VB.NET, performance of compiled code, watered-down but easier WPF and dynamic runtime library — that’s the game changer. It is an upcoming, compelling option for easily creating rich applications that run in browsers everywhere. Easy because developers get to use almost the same rich development tools, frameworks and languages that they use for rapidly developing desktop applications. The keywords are: Everywhere, Rich and Later.
Xceed DataGrid for WPF will not run on Silverlight. Xceed must build another data grid control targeting Silverlight. That other data grid control for Silverlight, though, may also run on WPF, it is a possibility. However, it will not offer the kinds of amazing experiences that are being prototyped for the next few releases of our WPF-only data grid. Silverlight v1.1’s leaner and easier WPF has its limitations.
The important thing to keep in mind at the moment is, Silverlight v1.1 is still heavily under development, and quite a while before being RTM’d. It is also part of a group of frameworks (along with Adobe’s Flex/Air, maybe JavaFX) that threatens Microsoft’s Windows cash-cow by rendering the underlying operating system less relevant. So a lot could drastically change, as the implications of Silverlight go deep. Waiting for Silverlight v1.1 to release and depending on that for your next applications is a hard-core early-adopter strategy. WPF was released January 2007, a new version is coming out imminently (so it is not a v1 anymore) and Visual Studio 2008 will have all the built-in tools that were missing. Its early-adopter stage is fading.
Imported from legacy forums. Posted by Odi [Xceed] (had 378 views)User (Old forums)MemberOctober 11, 2007 at 10:23 amPost count: 23064
Imported from legacy forums. Posted by jmcfetatwork (had 3250 views)
- You must be logged in to reply to this topic.