using EWS load on FileAttachment from linux/mono gives different result than on .net/windows RRS feed

  • Question

  • env:

    EWS 1.2, exchange 2007, windows/.net and linux/mono

    using the EWS 1.2 api to extract attachments from exchange gives different results on .net/windows as on mono/linux.

    the files differ at byte 8192, 16384, 20480

    So first after 8k block, then again after next 8k block and then 4k block again?!



    byte[] buffer = fileAttachment.Content;
    Console.WriteLine(buffer[8191]); //windows -> 50  | linux -> 50
    Console.WriteLine(buffer[8192]); //windows -> 9    | linux -> 59
    Console.WriteLine(buffer[8193]); //windows -> 54  | linux -> 44

    I already put the service.TraceEnabled = true;

    but i can't decode the format in of the content?

    any ideas?

    Tuesday, May 15, 2012 7:59 AM

All replies

  • The only type of encoding used in EWS is Base64 (which you should be able convert pretty simply) sounds like that's where it would be failing on Mono


    Wednesday, May 16, 2012 5:48 AM
  • Is there a way to get un undecoded content instead of the base64 decoded content of an attachment?
    Wednesday, May 16, 2012 2:09 PM
  • No not that i know of its more or less expected that the client should be able to handle the decode. The Managed API is just a wrapper for the underlying Web Service calls so you could build your own proxy and handle it manually or look at the Java managed API http://archive.msdn.microsoft.com/ewsjavaapi.


    Thursday, May 17, 2012 6:51 AM
  • Tried the Java managed API and this works like expected on linux.

    thanks for your feedback
    Monday, May 21, 2012 11:38 AM