A while ago I saw this decision chart to help choose a WCF default binding. Unfortunately I cannot remember where it came from. The problem I had with it was that you could only reach wsHttpBinding if you had to use interop. But you might need to use HTTP for a transport. Also the local option came too soon, where answering yes ruled out MSQM and P2P. So I had to change the original chart a bit. If there are any errors, please make a suggestion in the comments and I'll try to fix the chart.
Class-A logo in there because it's from our training material. You can use the chart for whatever you like though.
Dennis,
I have a question and since you are into WCF maybe you know the answer....
When you right click on an app.config it should be possible to open the file with the SvcConfigEditor.exe as an option in the context sensitive mnu.
But I couldn't find that option. Do you know how i can add it ?
@Patrick : You have to install the WF/WCF extensions to Visual Studio. You can find them here :
http://www.microsoft.com/downloads/details.aspx?FamilyId=F54F5537-CC86-4BF5-AE44-F5A1E805680D&displaylang=en
More info in an article from Mike Glaser :
http://bloggingabout.net/blogs/mglaser/archive/2006/11/06/.NET-Framework-3.0-has-been-released_2100_.aspx
However, this doesn't include everything. For example, the trace utility is in the SDK, which is 1 GB large! :) I hate that!
As I've been pretty busy, it's been a while since my last post in the WCF series. But let's have a look
I'm starting a series of posts about Windows Communication Foundation (WCF). The goal of the series is
Two more stops made and one more to go on the first tour of Bob & Chris' MSDN Roadshow! Portland,
Uriah, you're right, I'll have a look at the image. Thanks for your comment.
Also the CTP is the final version for Visual Studio 2005. There won't be any new version. For the next Visual Studio (currently codenamed "Orcas") these will be integrated...
In other words, it's safe to download the latest CTP.