Re: Webservice that references other .Net libraries

How can I ensure that the client has the class available?

Thanks
Kev

"Peter Rilling" <peter@xxxxxxxxxxxxxxxxxx> wrote in message
news:OJq0vxA0FHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
> Make sure your client has the returned class available so that it can be
> deserialized and instantiated, or make sure that you only return either
> primitive types or types that are available in the framework. Obviously
> if the class is not visible to your code, then it cannot create an
> instance of it.
>
>
> "Mantorok" <none@xxxxxxxxxxxxx> wrote in message
> news:diltp0$954$1@xxxxxxxxxxxxxxxxxxxxxx
>> 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: code access security across the network
    ... with web services, such as all of the various HTTP auth protocols (basic, ... only interaction with the calling code is data sent over the wire, ... data used to identify the caller can be spoofed by a malicious caller. ... client user identity and re-validating all data on the server side. ...
    (microsoft.public.dotnet.security)
  • Re: malloc()/realloc() - have I got this right?
    ... For some reason that is beound me you elected to ignore CBF's next ... The debate was whether the caller or the callee should disambiguate ... this to be done by the calling code. ... The client has to ...
    (comp.lang.c)
  • 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)
  • Re: Handling empty relation to child object
    ... but you won't have to check for Client = ... > In the calling code I do: ... > this will throw an error if, for whatever reason, the Client does not ... > How can I get it to return an empty string instead of having to do: ...
    (microsoft.public.vb.database.ado)
  • Re: Handling empty relation to child object
    ... but you won't have to check for Client = ... > In the calling code I do: ... > this will throw an error if, for whatever reason, the Client does not ... > How can I get it to return an empty string instead of having to do: ...
    (microsoft.public.dotnet.languages.vb)