«

I'm very confused with this. I have a .NET web service that I am trying
to pass a variant byte array to from the client side. If the signature
of the web service is set to accept an Object it seems to pass it in
but I can't access the array that should be in there. If I set the
signature as a byte array I get an error in webservice.htc. It seems to
be trying to encode the variable to base 64 and it fails when trying to
do a .length on it.

Am I supposed to convert this to Base64 or what? I would appreciate any
help with this as I am really in a jam.

Thanks

Alex

Hi,
I've had a similar problem with passing byte arrays as parameters in my
web services.
The solution i used was to manually convert the array of bytes as a
base64 encoded string and pass the string. Decoding on the receive.
My investigations into the nullified byte array led me to make this
post:
http://groups.google.com/group/micro...363e45fbf92e3d
hope my 'fix' helps.

I found some vbscript code which converts my array to base64. When I
pass it as a string and use the .NET Convert.FromBase64String to decode
this string I get an array with different values in it. Is there more
than one standard when it comes to converting into base64? Maybe I need
to modify the script code to comply with the .NET function?

Any ideas?

Thanks

wrote:

> I found some vbscript code which converts my array to base64. When I
> pass it as a string and use the .NET Convert.FromBase64String to decode
> this string I get an array with different values in it. Is there more
> than one standard when it comes to converting into base64? Maybe I need
> to modify the script code to comply with the .NET function?
>
> Any ideas?

<URL:http://en.wikipedia.org/wiki/Base64>


F'up2 microsoft.public.dotnet.framework.aspnet (where I don't read)

PointedEars