Todd Biske writes "Decision rights are certainly part of governance, but a view that makes them the defining part is wrong, in my opinion. If we focus too much on decision rights and not enough on decisions, we are at risk of creating fiefdoms of power that perpetuate the negative, command and control view of governance. If we focus on policies that enable anyone to make the correct decisions..."

David Overton writes "Remember that SBS 2008 is built on Windows Server 2008, Exchange 2007 and SQL 2008 (for the premium edition). This means that you are bound by the limits of those products. For SBS Standard..."

Kevin Remde writes "...like Small Business Server 2008, but bigger. Instead of 1-2 servers, it’s 3-4. Instead of limiting you to 75 users or desktops and under, we’ll let you grow to 300. Instead of costing the sum total of all the software you get, we’ll give you a good deal..."

Jesus Rodriguez writes "...The following code illustrates an implementation of the IWFExtension interface that executes a XAML-only workflow. In order to incorporate this implementation into the WCF runtime, we also implement the IExtension..."

Jimmy Bogard writes "...Just creating the IInstanceProvider isn't enough, we'll have to tell WCF to use our instance provider, instead of its own default instance provider. This requires a custom endpoint behavio...we'll use a custom service behavior through the IServiceBehavior interface. Here's the implementation of our custom service behavior:"

Bill Ryan writes "One of the big things you often hear about with WCF is self-hosting...I wanted to basically have a Winforms app host one service, and a Windows Service host the other part of the service, having the services talk to each other. The client winforms app would simply talk to the client service, it would never hit the Windows Service directly. So we built a client service and server service..."

Eugenio Pace writes "I liked the System.Xml.Linq classes very much... Using XElement & XAttribute was straightforward and compact:... The model should be fairly simple to extend to include support for other elements (radius, etc). or even the broader set of attributes in the SyndicationFeed class and related cousins."

Jesus Rodriguez writes "With these components we have, in my opinion, a good starting point to start combining durable messaging and services on different scenarios....on my first demo we started with a simple client-service interaction using workflow services...I shot down the service host for while I let the client sending a few messages that got stored in a MSMQ queue. After I started the service host back on, all the messages were delivered to the same service instance we were using before...."

Eric Shupps writes "In this example I'm showing how to use both a return value and throw an exception; use either or both according to your needs...This works for most SharePoint web services that return ErrorCode values (which some do not) so Your Mileage May Vary depending upon what you are trying to achieve..."

Rockford Lhotka writes "WCF is very cool, but configuring WCF can virtually derail a project. Even relatively simple-seeming configurations can take hours or days to get working. It is frustrating! And the most complex part is getting security working....probably the single best resource for information about configuring WCF security you'll find anywhere."

Ben Cline writes "Juval Lowy talked about the DurableService attribute, which can be added to a WCF service implementation to provide some of the persistence typically associated with WF in .NET 3.5. This is a closely related feature to BizTalk's concept of orchestration dehydration. For more information on DurableService see..."

Bill Ryan writes "I don't know if I love Powershell more than Windows Communication Foundation or WCF more than Powershell, but few things are cooler than using them together and this is one script you'll undoubtedly find helpful...."

Brian Loesgen writes "Done right, your enterprise becomes more agile, cost and time to deploy new functionality decreases, and you achieve the nirvana of code re-use we as an industry have been seeking for decades. Done wrong, and you'll squander precious people resources and budget on an initiative with little or no return. Mitigation: "boil the ocean" approaches fail. Think it all through, and then select some small services, then gradually pilot/deploy/build-up from there...."

Bill Ryan writes "...At the risk of sounding like a cheerleader for the new latest greatest technology from MS, I will say that once you get into WCF, you'd be hard pressed not to find it much simpler and intuitive than any of the older technologies....I'm trying to make this into a real demo app that's documented and can be done in steps - basically trying to turn it into a full walk-through. So I'm documenting it as I go along. I've gotten it completed through here - but I'm going to add Security, support for MSMQ and a few others..."

Brian Harry writes "The number one complaint that I hear is that building BizTalk with Team Build is very difficult. The underlying reason for this is that BizTalk does not use msbuild for building their projects. I'm very happy to say that I've just been informed that they will be getting it into..."