Architecture/SOA Blaine Wastell has posted that PAG planning an update of the Smart Client Software Factory to be released in late April of this year. They are encouraging feedback at http://www.codeplex.com/smartclient and enter critical items into the issue tracker ( http://www.codeplex.com/smartclient/WorkItem/List.... ). From where I sit, they have their Priority 1 stuff right with WPF Interoperability. We absolutely need to be able to move to WPF with the existing CAB/SCBAT infrastructure I have been listing posts on WS-RM and its implementation in WCF. Harry Pierson, has an autopost that builds on his recent epiphany about WCF and long running services. He speaks about his conversation with Shy and " At some point in the three years between March 2003 and February 2006, WS-RM went from being the enabler of long running services to "yet another misnamed WS-* protocol". And with it, WCF lost (never had?) the ability to support long running services (as I've written previously )." The main point is that it does not support RM-based durable messaging. As Harry says, "As I said before, lack of support for WS-RM based durable messaging isn't that big a deal. As long as you understand WCF's sweet spot - the current version's sweet spot anyway - and don't try and make it be something it's not, you should be fine. Furthermore, Shy mentions the need for an "interoperable Queued Messaging specification" and wrote that it's something he "expect that we will get to it in the near future". Here's hoping that spec is less flexible than WS-ReliableMessaging." CLR/Tools/Agile/TDD The most indispensable tool in the .NET universe, Reflector, has gone through a big update to V5! As Jamie states , "This is a significant update with lots of refinements and new features. Perhaps most significantly it includes support for C# 3.0 language features such as LINQ query expressions, lambda expressions and extension methods. See my screencast about using Reflector 5.0 from VS Orcas." He also
Read More...