-
| The Best from DevelopMentor | MORE |
- WPF Data Providers
One of the nifty new features of the WPF platform is the pluggable data providers. Data binding in WPF is extremely powerful -- I am constantly amazed at how much procedural code you can dump in favor of markup with creative bindings. Tags: NET;Code;WPF It ships with two out of the box: ObjectDataProvider: allows you to execute binding expressions against an object and it's methods. XmlDataProvider: loads an XML data source and makes it available as a binding source. State, Age, Income. We can get the data loaded into a collection source through the XmlDataProvider.
Mark's Blog of Random Thoughts - Wednesday, January 17, 2007 - WPF Data Providers
One of the nifty new features of the WPF platform is the pluggable data providers. Data binding in WPF is extremely powerful -- I am constantly amazed at how much procedural code you can dump in favor of markup with creative bindings. Tags: NET Code WPF It ships with two out of the box: ObjectDataProvider: allows you to execute binding expressions against an object and it's methods. XmlDataProvider: loads an XML data source and makes it available as a binding source. State, Age, Income. We can get the data loaded into a collection source through the XmlDataProvider.
Mark's Blog of Random Thoughts - Wednesday, January 17, 2007 - Playing with VS.NET 2008.
I've been playing a bit with VS.NET '08 June CTP lately and noticing several nice improvements - the Cider WPF add-in especially seems to have better integration with the code window. Tags: NET WPF For example, double clicking on an element now creates the code-behind handler (finally!). The layout support is much better as well - you finally get the drag handles and positioning lines. The property sheet seems a bit sketchy right now - I see how Blend has certainly influenced it (as the code apparently is coming from that product), but I find Blend to be easier to work with there.
- Christmas comes early: Microsoft releases Visual Studio.NET 2008
There’s a ton of new features and enhancements in this release that makes it almost a no-brainer to upgrade - I thought I’d take a moment and list my top ten favorites in no particular order: #10: WPF designer (“Cider”). spend a lot of time on rich-client island and compared to the embarrassing support for WPF provided for VS2005 (through an add-on) VS2008 just plain rocks. 9: WPF and Windows Forms integration (“Crossbow”). Hand in hand with the designer view, VS2008 improves the designer experience for Windows Forms to WPF integration. 7: Multi-framework targeting.
Mark's Blog of Random Thoughts - Wednesday, December 19, 2007 - WPF Pong
This got me thinking about writing a classic game using WPF, not being much of a games writer I kept things simple and decided to implement the classic game Pong.My main aim is to continue to ramp up on WPF, one area I wanted to explore further was the use of Content Templates and styles, what I wanted to be able to do was not only clearly separate UI layout from UI behaviour but also allow different Skins to be applied to the game one being the classic black and white look another being a more 21 st Centaury look and feel. First to 9 wins.
.NET Mutterings - Friday, January 5, 2007 - WPF Extension method
I used my first extension method yesterday with WPF. So I refactored my code once more into a separate assembly, but placing the code into the System.Windows.Controls namespace, thus whenever I use WPF controls and reference my additional extension assembly I get my new methods. I wanted to bring a control to the foreground, that means changing its position in the child list to the last child. Parent.Children.Remove(element); Parent.Children. Add(element); What I would prefer to do is call SendToFront on the collection with the appropriate child.
.NET Mutterings - Wednesday, October 10, 2007 - Playing with VS.NET 2008.
I've been playing a bit with VS.NET '08 June CTP lately and noticing several nice improvements - the Cider WPF add-in especially seems to have better integration with the code window. Tags: NET;WPF For example, double clicking on an element now creates the code-behind handler (finally!). The layout support is much better as well - you finally get the drag handles and positioning lines. The property sheet seems a bit sketchy right now - I see how Blend has certainly influenced it (as the code apparently is coming from that product), but I find Blend to be easier to work with there.
