Welcome to Windows Communication Foundation (WCF)
Top Tasks :

WCF Community Bloggers

Browse by Tags

All Tags » Financial and B... » CAB   (RSS)

  • PDL from .NET, Reporting, BIRT, Telerik, Orcas, URL Data Services and Astoria!

    There! Enough things in one title? The thing is that Steve Eichert and my whirlwind day covered all of that and more. Let me explain. So, for two weeks, Steve and I have been off discussing/pairing on some big ticket "Infrastructure" items. There are many things on the list and we have been applying both heavy design discussions on the whiteboard with practical prototypes or solutions. These areas have covered the whole spectrum from what will the world look like in 3 months, 6 months, a year, 3 years to caching architecture to workflow to to parallel computing to replacements for CAB to Services to reporting and much more. Yesterday, we spent a day on our "Reporting Strategy or Reporting Architecture." Being a large Enterprise platform, it is very important to have a comprehensive Reporting story on both the Smart Client side as well as on the Server side. I'll just leave it very generally that there are certain kind of reports for us that are really "Statements" and then Ad-Hoc Reporting. My story for most of the last year and half has been SQL Server Reporting Services . I have had good experiences with it at Adesso even as reporting on Oracle. Of course, there is that "small footprint" of having a "reporting database" for SQL Server but virtually all the "Enterprise Reporting" solutions require some footprint. However, lately it has become totally apparent to us that virtually every single Bank customer of ours is an Oracle shop only other than very small hedge funds and we have really de-emphasized SQL Server. Its still in our CI build and code gen but we are now optimizing for Oracle. Anyway, we wanted to keep the Statement stuff simple. Forget a whole reporting thing for that. We really only need to generate pretty much canned statements with customizable logos and footers. So Steve and I began to look at a whole bunch of HTML to PDF or .NET libraries for PDF generation. We ended up feeling real good 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