|
|
Browse by Tags
All Tags » CAB » SOA (RSS)
-
Multithreading and Concurrency Software Transactional Memory Part IV - Thread-Bound Transactions Software Transactional Memory Part V - Integration with System.Transactions Parallel LINQ Restating the Concurrency Problem Herb Sutter is starting a new column on Effective Concurrency Shared nothing parallel programming \ Software Design/Smart Clients/CAB/Web Clients Using NUnitAsp to test Pages w/Forms Authentication Build your own CAB #12 - Rein in runaway events with the "Latch" Build your own CAB #13 - Embedded Controllers with a Dash of DSL A whole pile of goodness taking CAB forward from the folks at SCSFContrib . which includes A full implementation of the UI layer for CAB done in WPF with 100% code coverage in tests!! (see Bill's post ) WCF/SOA ChannelFactory Behaviors David Chappell declares the REST vs. WS-* War over . Here's hoping Orcas/LINQ ScottGu continues his excellent series with LINQ to SQL (Part 4 - Updating Our Database) ADO.NET Entity Framework The ADO.NET Entity Framework June 2007 CTP is now available. See the team blog for changes Ruby/Subversion My team-mate Steve points to some great resources on the Beauty of Ruby as well as finding a Web-based Subversion Browser Other Link Blogs Interesting Finds: July 10, 2007 PM Edition Daily Grind 1182 Technorati Tags: CAB , Ruby , Concurrency , Microsoft .NET , Software Transactional Memory , PLINQ , NUnitASP , Software Design , Design Patterns , Ruby on Rails , Subversion Read More...
|
-
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...
|
-
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...
|
-
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...
|
-
Both the July drop of the Web Service Factory or Service BAT is out and the June SCBAT are out. I am super excited about this as it is nearing V1 and we are using both of these in production code. I have been blogging about the Service Bat since the begining . I talked about my SCBAT experiences here and that the SCBAT has helped us reduce our UI and CAB costs 5 to 1. Remember to install the the new June 2006 release of the Guidance Automation Extensions and Toolkit , first! A couple of real cool things on the Services BAT according to Tom : The installation process has been streamlined And the biggest news is that the Service Factory now has a brand new guidance package dedicated to helping you build data access layers using ADO.NET 2.0. The goal of this guidance was not to be an object-relational mapping framework or an entirely new approach to data access. Instead it's designed to take out some of the repetitive and error-prone work of creating a data access layer by hand, by helping to create some (but not all) of the key classes used in a data access layer. Most of you are probably already aware that the choice of available technologies for building data access layers will be changing significantly in the future with the advent of LINQ to ADO.NET . We're already working with these teams to start planning for these technologies, and we'll be publishing samples that show how the Service Factory guidance will look in a LINQ to ADO.NET world. I said this in all three of my recent INETA talks: PAG is the best group in Microsoft right now. Technorati Tags: Smart Client , CAB , Architecture , Software Architecture , ADO.NET , LINQ , SOA , WCF Share this post: Email it! | bookmark it! | digg it! | reddit! | kick it! Read More...
|
|
|
|