Don't use ASMX web services. Go with Windows Communication Foundation. http://www.west-wind.com/presentations/foxdotnetwebservices/

Craig,

Are you using WCF?

While I like the WCF model very much, I don't think it's a total slam dunk, depending on what the requirements are going to be.

FYI, you do lose a little bit of functionality by opting for WCF over ASMX web services. ASMX web services allow a developer to easily test a web service by loading the browser, entering test parameters, and seeing your result set. You can't do that with WCF. That's not a show-stopper, as one can build other methods to test. However, this been a rather unpopular discovery, and I know experienced developers who don't want to touch WCF because of this.

(I also know some hardcore WCF people who say, 'you should never have been testing web services that way to begin with', which I find a real chin-wagger).

I have a community presentation I've been doing, "Intro to WCF". Almost all who have been doing remoting, love WCF. Those currently using web services, it's roughlyt 60-40 in favor.

Kevin