Welcome to Windows Communication Foundation (WCF)
Top Tasks :

WCF Community Bloggers

Browse by Tags

All Tags » New and Notable » Smart Client   (RSS)

  • New and Notable 146

    Ah Saturday morning where we can sleep in, ah no wait...I have kids to wake me up at the crack of dawn... Software Architecture The PAG folks continue to deliver their goodness with their first weekly drop of the new version of the Smart Client Software Factory and they looked like they brought over some of the cool stuff from the Mobile version: What’s New In this drop, you have the first look at: • New Application Blocks. We have ported over four application blocks that were previously available as part of the Mobile Client Software Factory. We may refactor, remove, replace, this code in the future (we value your input), but we currently have the following: o Disconnected Agent Application Block. This application block provides management features for execution of Web services from occasionally connected smart clients. With a disconnected service agent, the device can maintain a queue of Web service requests when offline (disconnected) (emphasis mine) and then replay them when a connection to the server application becomes available. o Connection Monitor Application Block. This application block monitors and exposes the available connections and the associated networks. o Endpoint Catalog Application Block. This application block provides features to expose the physical addresses and other details of remote services. o Data Access Application Block. This application block provides support for SQL Server Compact Edition. This application block will be replaced when the factory migrates to the next version of Enterprise Library. Jeremy Miller continues his excellent posts and talks about something Steve and I approach in our architecture: Don't Let the Database Dictate Your Object Model . I have to admit to being dragged a bit by Steve into this approach with OR/M and dropping the whole data-centric database-out view I have had for many years. Also see his My Least Favorite Kind of Requirements Undocumented WCSF Feature: Global Exception Handling Udi tackles Can, or Read More...
  • New and Notable 145

    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...
  • New and Notable 142

    Data/ADO.NET Orcas Two from the ADO.NET team: Entity Client and Nulls - LINQ to DataSets Part 3 Software Architecture/SOA/CAB Udi answers, Can or should SOA be implemented without Web Services? David Chappell on The Three Faces of SOA Eric Newcomer: WS-* vs. REST is not the question Another architect with a chronicle of How CAN and TDD helps doing better designs WCF/CardSpace Richard Turner gives an insightful report on RSA2007 especially on the "demo showed Wachovia 's website running on Corillian 's online banking platform using Arcot Systems ' security engine to generate managed cards and process token requests." Corrillian and Wachovia's work will be important for all of this in this sector as more and more backs embrace CardSpace and Identity management. We are seeing a lot of movement in this area. Jorgen provides some great links on Interoperability with WCF . This is an area that I am becoming more involved with Java systems communicating with our WCF Services. Dr. Nick continues with More Poison Message Handling Tomas on Writing a WCF Transport Channel - Part 1 Agile Architecture Uncertain Planning Nick talks about The minimum amount of architecture needed for Test Driven Design . .NET Framework 3/WF .NET Framework 3.0 training kit for WF, WCF and CardSpace [via Mike ] .NET 3.0 Middleware Technologies Day: Third Incarnation David Chappell: Why Workflow Matters WF, WCF and CardSpace training materials posted Technorati Tags: .NET , Smart Client , PAG , CAB , Software Architecture , Windows Communication Foundation , WCF , Windows Workflow , WF , Agile Architecture , TDD , .NET Framework 3 , ADO.NET , Orcas , Microsoft I'm listening to Street Life by Roxy Music on the album Stranded (Remastered) Share this post: Email it! | bookmark it! | digg it! | reddit! | kick it! Read More...
  • New and Notable 141

    Found some time to blog. Smart Client/UI Architecture V2 of the User Interface Process Application Block (UIPAB) is out from PAG [via Mike ]. I must confess to being confused on how this is different than CAB as "designed to abstract the control flow and state management out of the user interface layer into a user interface process layer," which CAB does with MVP as well until I saw. "helps you write generic code for the control flow and state management for different applications types (for example, Web and Windows) and helps manage user's tasks in complex scenarios." So which do you use in Smart Clients and why? Software Design/DDD As I have stated our Architecture reflects a strong, "proper" DDD Layer . Teammate Steve, is also a big believer and we have both lost focus a bit on it as we have been swamped with other things. His post is a good reminder to check out the experience reports on the DDD site. One reader once said I was using buzzwords. I think not. Especially in a large Financial Collateral application it is vitally important to use the UbiquitousLanguage of the actual Collateral banking domain that the analysts use and design a business layer reflecting that. And yeah, I'm astonished how many .NET developers have never even heard of the fundamental DDD patterns when I talk about SOA/Architecture for INETA around the country Data/OR/M One thing that goes well with a true domain layer is an OR/M implementing the Domain Mapper pattern . The ADO.NET team (along with some bloggers), which lately found religion, talks about the Entity Data Model 101 - Part 2 WCF/Indigo Confused about all the many WCF configuration options? Tomas has an excellent post on understanding the admittedly complex WCF configuration schema. In return, you get fine-grained control Technorati Tags: .NET , Smart Client , PAG , CAB , Software Architecture , Windows Communication Foundation , WCF , Microsoft I'm listening to Paranoid Android by Radiohead on the album Edinburgh, Meadowbank Read More...

Copyright © 2006 Microsoft Corporation. All Rights Reserved. | Terms of Use | Privacy Statement | Contact Us