Showing posts with label WCF. Show all posts
Showing posts with label WCF. Show all posts

Wednesday, August 10, 2011

SOA'izing MSMQ with WCF

Microsoft Message Queuing’s (MSMQ) integration with the Windows Communication Foundation (WCF) is extremely powerful. It enables MSMQ developers to write fault-tolerant, service-oriented applications and provides a robust extensibility model developers can use to improve any system’s capabilities – including MSMQ’s. In this video and corresponding sample we'll convert a System.Messaging application into a WCF Queuing application, enable that application to overcome MSMQ’s 4mb message size limitation with a prototype chunking channel, and integrate it seamlessly with existing MSMQ applications.

More here...

Thursday, March 10, 2011

Exposing a WCF Service With Multiple Bindings and Endpoints

Windows Communication Foundation (WCF) supports multiple bindings that allows developers to expose their services in a variety of ways. What this means is a developer can create a service once and then expose it to support net.tcp:// or http:// and various versions of http:// (Soap1.1, Soap1.2, WS*, JSON, etc). This can be useful if a service crosses boundaries between intranet and extranet applications for example. This article walks through the steps to configure a service to support multiple bindings with Visual Studio 2008 and the .Net 3.5 framework. For those that want to jump directly to the sample solution it can be found at the end of this article.



Wednesday, May 12, 2010

Wanna learn WCF?


Check out Dennis van der Stelt's blog if you are interested in learning about WCF.


Thursday, July 23, 2009

WCF Hosting

Windows Communication Foundation (WCF) Services can be hosted with Internet Information Services (IIS); with the new Windows Activation Service (WAS) installed with IIS 7.0; or with any managed application process including console, Windows Forms, Windows Presentation Foundation (WPF), or managed Windows service applications.

Selecting the right hosting environment for your services is a choice driven largely by deployment requirements related to transport protocol and operating platform.

A summary of hosting options and supported features:

FeatureSelf-HostingIIS HostingWAS Hosting
Executable Process/ App DomainYesYesYes
ConfigurationApp.configWeb.configWeb.config
ActivationManual at startupMessage-basedMessage-based
Idle-Time ManagementNoYesYes
Health MonitoringNoYesYes
Process RecyclingNoYesYes
Management ToolsNoYesYes



A summary of hosting options based on operating platform and communication protocol:

Operating PlatformProtocolHosting Options
Windows XP/SP2HTTPIIS 5.1 or self-host
Named Pipes, TCP, MSMQSelf-host
Windows VistaHTTP, Named Pipes, TCP, MSMQWAS or self-host
Windows Server 2003HTTPIIS 6.0
Named Pipes, TCP, MSMQSelf-host
Windows Longhorn ServerHTTP, Named Pipes, TCP, MSMQIIS 7.0/WAS or self-host





MSMQ, WCF and IIS: Getting them to play nice

I was doing some research on Hosting my WCF Service in IIS 6. My service supports both synchronous and asynchronous behavior (using msmq).

Below is a summary of hosting options based on operating system platform and communucation protocol:

Operating Platform Protocol Hosting OptionsWindows XP/SP2 HTTP IIS 5.1 or self-host Named Pipes, TCP, MSMQ Self-hostWindows Vista HTTP, Named Pipes, TCP, MSMQ WAS or self-hostWindows Server 2003 HTTP IIS 6.0 Named Pipes, TCP, MSMQ Self-hostWindows “Longhorn” Server HTTP, Named Pipes, TCP, MSMQ IIS 7.0/WAS or self-host


MSMQ, WCF and IIS 7
I found this article that contains very good information on getting MSMQ, WCF and IIS 7 (WAS) to play nice.


Also Read:

Friday, May 8, 2009

Communication options with WCF

Great introduction to Windows Communication Foundation (WCF) Services by .


MSDN: What Is Windows Communication Foundation?