Blogger :
Thinktecture Blog
All posts :
All posts by Thinktecture Blog
Category :
WSE
Blogged date : 2006 Nov 21
OK, there is one library I wrote a long time ago which has a lot of fans:
DynWsLib.
This library is for invoking your Web Services
dynamically without having to generate a client-side proxy class
at design/compile time with
WSCF,
wsdl.exe or Visual Studio.
No need to know the exact Web Service description and endpoint at compile/design time.
Just get your WSDL, specify the service (binding) to use and the
operations to call, and voila! The library can be especially
useful in testing scenarios.
Now, I have not been working on the lib for a long time (just released a .NET 2.0 compatible version some time ago).
Recently, two great guys,
Pascal and
Anthony, took the next step and built upon DynWsLib what they call the
ProxyFactory. Go and grab it!
The emergence of the WCF platform announces the unification of all communications technologies provided by the .NET platform in a common foundation and so their decline, WCF’s adoption curve will be slow enterprise wide. So it is still safe bet to develop a library to leverage .NET 2.0 generics and SchemaImporterExtension mechanisms to offer a similar developer experience.
Such a library already exists to target web services communication, it was developed by Christian Weyer but as opposed to the WCF ChannelFactory<TChannel>, his library doesn’t provide an effective mechanism to handle specific types during the proxy generation process. This is what is tackled by the ProxyFactory project in taking advantage of SchemaImporterExtension mechanisms. Futhermore, alternative communication techonologies are targetted such as Remoting and WSE.
Contents
ReBlogger Contents
Email TopXML