Getting Started with Windows Communication Framework

.NET 2.0 Distributed Application Programming Sample Code

Dan Wahlin's WebLog — Mon, 09 Jul 2007 18:05:28 GMT

For those taking the Distributed Application Programming course this week with me (or anyone else who

re: Getting Started with Windows Communication Framework

Rick G. Garibay — Wed, 25 Apr 2007 04:34:06 GMT

Hey Dan,

Great post.

Couple of questions:

>> For example, a local ASP.NET application could call the business layer code directly rather than having to serialize/deserialize messages by calling the WCF service

Using service stubs to delegate out to a BSL is a practice I used exclusively with ASMX, however with WCF, my thoughts are that since the service class that implements the service contract is simply a class (and carries no inherent association to a service), it lends itself just fine to in-process instantiation. My understanding is that this removes a once necessary layer to avoid service activation/serialization/deserialization. For example, my unit tests exercise a service both directly (as a class) and out-of-band (as a service endpoint). If I wanted to call the service in process, I *could* do so as a class/component, but IPC would probably be better for consistency. What do you think?

>> typically prefer to model my data contracts using XML schemas (.xsd files). This way I know that messages exchanged between the client and service are based upon global standards which helps to eliminate interop issues across different platforms.

I've wondered if this is more of a formality with WCF, and your post along with a recent discussion with Jeff Hasan seems to support using XSD even with WCF.

So it sounds like WCF simply provides policy compatability based on bindings and message interop can only truly be guaranteed using XSD. So really, System.Runtime.Serialization doesn't do any more to guarantee message level interop than System.Xml.Serialization, only XSD can accomplish this, correct?

Also, other than acting as a template for the Data Contract (and the possibility for document-centric validation if needed), do the XSD schema just remain an artifact within the domain-specific class (entity) libraries? This is what I have done in the past, but I have found that avoiding the temptation on teams to "just update the class" requires significant discipline. But then again, I guess so is the price of SOA ;-)

Thanks again for a great post and I look forward to your thoughts.

re: Getting Started with Windows Communication Framework

Andy Koval — Fri, 09 Mar 2007 20:12:11 GMT

Hi,

I'm new to WCF. If I've got an observerableCollection that I'm using in WPF, would I adorn the collection with [DataContract] and [DataMember] attributes. If so how...?

re: Getting Started with Windows Communication Framework

dwahlin — Mon, 22 Jan 2007 22:52:09 GMT

I'm guessing that a namespace is causing the issue potentially although to generate my "model" classes I'm still using xsd.exe for the most part.

re: Getting Started with Windows Communication Framework

Kenny — Fri, 19 Jan 2007 16:14:00 GMT

Hi, you wrote, that you use xsd files for the data contracts. Me too ;o). I used the svcutil- tool, but it generates an error - message:

One of my complex types can`t get imported. Is there another way to solve this problem (datacontract.xsd to *.cs - class), and how can i declare my [data member] in this XSD-file???

Getting Started with Windows Communication Framework

DotNetKicks.com — Mon, 30 Oct 2006 23:58:05 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com