Disclaimer: The following post will probably only make sense to a few people. If you don’t know the difference between a method and property, avert your eyes.Yesterday I set out on a mission to programmatically list my weblog on Weblogs.com afterevery time it was updated. Normally this would be very easy if I was using a webloggingtool, but alas for some reason I try to complicate my life by doing everything myself.So, with that in mind, I read up on the specs andsaid to myself “ahh, it can’t be that hard to send an XML-RPC request via .NET, right?”Wrong. Wrong because for the life of me I couldn’t seem to find the WSDL file so thatI could easily create a proxy class to work with. Wrong mostly because Dave Winerprobably enjoys being a pain in my ass. In an InfoWorld article he says “WSDL (WebServices Description Language) was invented in such a way that it will only work inJava and .Net environments.” Thus, I guess he decided not to create one. My argumentis that it wouldn’t hurt to have one. Anyway, giving up on the 5-minute solution thatthe WSDL would have provided, I decided to try and create the actual SOAP requestmyself. (I’d do this before messing with XML-RPC) I was going to try to create a SOAPenvelope, but later found out that practically no one is doing this past ASP and VB6.(reason being because of the advent of .NET web services and the trusty WSDL file).So that meant I couldn’t find any code samples and couldn’t figure it out. Finally,after realizing that I couldn’t be the only one with this problem, I searched forsomeone who had the bright idea to write a WSDL themselves. Success.After mating the WSDL with WSDL.EXE, I had a shiny new proxy class to interface withweblogs.com :) Needless to say, the actual coding took less than 5 minutes.