Consuming XML-RPC web services with C# - Part 3 - let others do the work

At Part 1 and Part 2 I have shown the raw way and the object oriented approach to consume xml-rpc web services.

This time, we take a look at a helper to simplify the process of developing and consuming XML-RPC web services.

Consuming XML-RPC web services with C# - Part 2 - the OOP approach

At Part 1 I described a basic way to call and consume data from xml-rpc web services based on XML string operations.

This can be only the first approach. It's unhandy and not easy to maintain.

The next level for me would be to cast this into an object oriented data structure that could be easily maintained and customized for special needs.

At this post I try to show my object oriented approach to consume such services.

Consuming XML-RPC web services with C# - Part 1 - the rough way

While dealing with integration of Bugzilla as data provider within BugtraqPlugin (which I described here) I encountered that bugzilla has an XML-RPC interface. Not this bad, but

How to perform XML-RPC calls with c# and .NET?

It's a simple task to get access on soap web services because it provides a description of it's own interface through a wsdl definition, so you easily can generate proxy classes for such a case.

But whats about XML-RPC web services? Here is just a sample practiced on bugzilla web service.

Tortoise SVN Plugin for issue tracking system

In the field of software development it is enssential that source code is managed through a version control system. Without that, you loose an easy way to track changes and versions of your project.
(But discuss that is not the intention of this blog post, so skip comments about that.)

On the other hand, a version control system is not the right tool to manage project dependent things, feature requests and to track bugs. So professional teams use also a project management tools in combinition with bug tracking systems.
(To discuss the pro an cons of different systems is also not the intention of this post, so ...)

And now, one question:  
What it will be, if you combine these applications and let them communicate in two ways?