Profile_bird

Hey there! ReedCopsey is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving ReedCopsey's tweets.

Already using Twitter
from your phone? Click here.

ReedCopsey

  1. RT @JesseLiberty: Wanted: Volunteer readers for book on Silverlight 4. Requires serious time for next few months. jliberty@microsoft.c ...
  2. @kiwipom Thanks! It's something I haven't seen, so I'm going for a good explanation of why #MVVM works. Needed to show what not to do :)
  3. Blogging about moving from WinForms to #WPF with #MVVM in #csharp - Part 4, Data Binding, is online http://reedcopsey.com/?p=104
  4. @JesseLiberty For most purposes, I think tools are the right approach - especially if you're talking to people just starting with SL or WPF.
  5. @JesseLiberty I see @Pete_Brown's point. It's about whether you're teaching somebody to use the framework, or to extend it. Both are valid.
  6. @gblock Will this be (mostly) API compatible and functionally equivalent to the SL 4 PartInitializer? That would be very appreciated.
  7. MMM - Enjoying the first cup of coffee in my new #DotNetRocks mug. Thanks @carlfranklin and @richcampbell!
  8. Blogging about moving from WinForms to #WPF with #MVVM in #csharp - Part 3, WPF version 1, is online http://reedcopsey.com/?p=103
  9. Blogging about moving from WinForms to #WPF with #MVVM in #csharp - Part 2, Windows Forms, is online http://reedcopsey.com/?p=100
  10. @WayneBerry It's probably a good idea to rinse the rice first, in which case, it wouldn't matter. http://bit.ly/6PrO6x
  11. Very nasty concurrency question - It's always difficult to explain how something that looks so wrong is really correct: http://bit.ly/859NCB
  12. Blogging on moving from WinForms to #WPF with #MVVM in #csharp - Intro (http://bit.ly/4yLQ7K) and Part 1-Model (http://bit.ly/5993B3) online
  13. RT @onovotny How about putting INotifyDataErrorInfo in .NET 4? #WPF needs it at least as much as #SL4
  14. Going home from #PDC09. It's been great!
  15. Unsealed attributes in MEF, now, lets you define your own customized attributes. #MEF #pdc09
  16. Automatic interface proxies in #MEF == pseudo duck typing. Very nice! #pdc09
  17. Term of the day (by @gblock) "Ball of mud driven development" #pdc09
  18. Nice. #MEF is in the box in #SilverLight 4. #pdc09
  19. Sitting in Hall F, anxiously awaiting @gblock's #MEF talk. #pdc09
  20. "Sharing is typically a good thing", but in parallel, it's "the source of all evil" - Axum talk at #pdc09