Awhile back, I posted on Dynamically Invoking Web Services using ASMX. To do this, we used a little nasty bit of CodeDOM trickery and reflection, something that just isn't needed with WCF. Take a look at how much easier this is using WCF.
BasicHttpBinding binding = new BasicHttpBinding(BasicHttpSecurityMode.None);
IChannelFactory<IRequestChannel> factory = binding.BuildChannelFactory<IRequestChannel>(new BindingParameterCollection());
EndpointAddress address =
IRequestChannel irc = factory.CreateChannel(address);
using (irc as IDisposable)
XmlReader reader = XmlReader.Create(new StringReader(
Message m = Message.CreateMessage(MessageVersion.Soap11,
Message ret = irc.Request(m);
//close the factory
To test this, I simply used Visual Studio 2008 to create a new WCF Service. I changed the binding from wsHttpBinding to basicHttpBinding, and the rest stays the same.
One of the neat things about the original post was that you could download the definition and compile it. You could still do the same operations here and use that to serialize into an object used in the CreateMessage method.
PingBack from http://blog.a-foton.ru/index.php/2009/01/21/dynamically-invoking-web-services-with-wcf-this-time/
Is there an advantage to dynamically constructing the service operation over binding with service references directly?
In my opinion, not for the majority of cases. However, there have been several customers who came up with cases where they wanted their own "Add Service Reference" type of functionality at runtime.
I have gotten quite a few emails on the previous post, thought it was time to write up the WCF version as well.
When I work with a lot of folks on services, I find that the Managed Services Engine (http://www.codeplex.com/servicesengine) actually fits their problems more cleanly, providing virtual services instead of pushing the brunt of the work into the client.
Thank you for submitting this cool story - Trackback from DotNetShoutout
Development Merlin Wizard Framework - A framework for easily making wizards in .NET. LINQ to SQL templates