The Patterns and Practices site announced the organization of the Application Blocks into Enterprise Library 1.0. Avanade Enterprise customers get it late 2004. The rest of the world gets in early 2005. The GotDotNet blurb says:
Enterprise Library 1.0 will include blocks for Data Access, Exception Handling, Caching, Configuration, Logging & Instrumentation, Security and Cryptography, in a single integrated download. The Library will feature improved consistency, extensibility, integration and ease of use, and will include a GUI-based configuration editing tool, generally eliminating the need to hand-edit XML configuration files for the blocks.
Christian Weyer suggests passing message objects that are XmlSerialization attribute encrusted back and forth from ASMX web services.
Well...I suppose it's easer to read than staring at WSDL. However, it's certainly not as easy as:
[WebMethod]
public string HelloWorld()
{
return "Hello again...";
}
Dino Chiesa's response to my WSDL First: A road to Pain? posting was to do both together. That is, do your web method, look at the WSDL, and change your web method to improve the WSDL.
Of course you can't do [SoapDocumentService(ParameterStyle=SoapParameterStyle.Bare)] when you have multiple parameters when you do it. It's a lot easier to read and write in code, though. Maintenance of the contract, however, may be another story.