Gerry, the .NET framework has all of this building and parsing built-in, as well as auto-generation of web service clients and servers. With UO.NET or mv.NET you can create a front-end to your app with absolutely no concern for XML or SOAP envelopes. You can get your HelloWorld function within minutes.
mv.NET uses UO.NET as a raw data pipe. Think of mv.NET as a suite of libraries that make development much easier for many purposes. For your purposes you don't need mv.NET, but I encourage you to consider mv.NET as a superset over UO that will save time with a lot of projects. For example, mv.NET faciliates both inbound and outbound web services. Email me for an mv.NET FAQ, which includes pricing info and a link to download documentation and a free trial of the software. Nebula R&D is a worldwide distributor of mv.NET, providing installation assistance, product support, and development and training services for .NET and mv.NET. Code samples provided by Nebula R&D include ADO.NET, ASP.NET, and Web Services, using VB.NET and C# for side-by-side comparison. HTH Tony Gravagno Nebula Research and Development TG @ removethispartNebula-RnD.com gerry wrote: > We have some older code that works with a web service via the CallHttp > API. > I am looking at some newer things and decided to look into using the > SOAP API instead of CallHttp mainly because I assumed that the SOAP > API would make things 'cleaner' in particular when accessing the > returned data. > However as far as I can tell, it has actually makes it messier. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
