I have this web service I want to use. The supplier only provides a PHP example to use the API. It is not a standard SOAP or REST service, but a custom Http POST based command. This means that you that you either have to write

Calling the API

Because every effort is done to maintain the original architecture by the conversion tool. The convertor tool added a PHP namespace containing extra support classes for duplicating the original (php) functionality. The previous line of code is thus converted to:

My problem with the wrapper functions created by the convertor tool, is that they use System.Object parameters and also return a System.Object. So for readability and maintenance reasons, I started immediately converting this to some strongly typed code.

Conclusion

I was very pleased with this tool. I saved literally hours typing, and it took me (only) a few hours of refactoring. Refactoring meant:

removing unused functionality (magicQuotes, cURL, …)

removing unnecessary type checks using Relfection

removing calls to wrapper functions when I had decent managed .Net code available in my library

And just now I started thinking that it may have been faster implementing a custom WCF implementation.