No, it shouldn't be different. The UV service exposes a WSDL definition of the web service (I don't recall how but I'm sure someone here can say). See my text which you snipped below ( *grin* ) where I describe how to create a web service client from VS using a URL. Point that to your UV WSDL and it will generate the C# client as you describe here. The only issues I've seen in stuff like this is with namespaces and odd attributes on nodes rather than nested nodes. For example: <some-ns:address city="foo" /> compared to: <address><city>foo</city></address>
HTH T From: Rudy.Cooper I’m using soap. I have a service in UV that get’s called from a Seibel app, which has been running for several years now. I created the soap server using the UV web services developer. It works great for the Seibel app. So now I want to consume that same web service but I want to create the client in vs2010 using c#. So would consuming it be any different if the web service was written in UV as opposed to one that is an asmx web service? From: "Tony Gravagno" I have a video which shows how to create and consume ASMX web services in just a few minutes: http://nebula-rnd.com/products/gallery.htm It's using mv.NET… _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
