Webservice that references other .Net libraries

Hi all

I have a web service and it is going fine until I call a method that returns
an object that is based on a class from a referenced .net assembly.

The problem is my calling code doesn't know anything about the class that
the web-service is using, how do I ensure that my calling code is aware of
the classes/objects being returned by the consumed web-service?

Hope that makes sense
Kev


.

Relevant Pages

  • Re: What design pattern(s) to use here?
    ... There is a class "ClassA" with some properties & a method ... in the web service method itself a kind of stand-in for the original user as ... Please stop using the term "Facade." ... way to "fool" the calling code because it thinks that it is using one ...
    (comp.software.patterns)
  • Re: returning custom class from web service
    ... I can't help you with being able to call public functions. ... As far as returning the class, in your calling code, you can't ... refer to the class assembly itself like you do in your web service. ... Also I want to call public functions of that type at client ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Please Wait Image Control
    ... Is it possible you could give me an example of the calling code. ... set multiple update panels to trigger when a page loads? ... For web service interaction from ASP.NET AJAX: ... I have a webservice that returns a bytefor an image. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: How to return XML Document from web service.
    ... then your web service returns an XMLDocument. ... the calling code would look something like: ... Dim xmlDoc As Xml.XmlDocument = ws.someMethodThatReturnsAnXMLDocument ... Public Function GetWebOrdersAs XmlDocument ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: code access security across the network
    ... There is no reliable way to identify calling code over a network. ... used to identify the caller can be spoofed by a malicious caller. ... your efforts would be better placed on ensuring that your web service ... this would involve not trusting self-declared client user ...
    (microsoft.public.dotnet.security)