Hey guys,
We recently updated our Aspose 5.7.0.0 library to 6.0.0.0 just before the holiday break and had to roll the entire changeset back because testing determined that thousands of email messages were missing.
I did a few experiments this morning and it’s now very clear what’s happening. With the 5.8.0.0 release, you guys introduced the paging feature. One would expect that adding a new feature like this would allow pre-paging API’s like ListMessages to work as before. I debugged into our Aspose/Exchange code and its pretty obvious that the old ListMessages signature is now returning a partial/paged list. When testing folders with some 15k+ messages under the debugger, I can see that the new LastPage property is set to false, which makes me think you’re merely forwarding this call into the new paging ListMessages overloads.
This is the ListMessages signature that we were using…
ListMessages(folder, ExchangeListMessageOptions);
I then went ahead and changed the code in question to enable/support paging and it works; however, our usage of Aspose.Email requires us to get attachment information and the paging feature change that was introduced with 5.8.0.0 does not allow you to support both paging and ExchangeListMessageOptions (please review all overloads to fully understand this problem). In short, we’re pinned into a corner because the old code no longer works and adapting to the new paging feature doesn’t allow us to retrieve attachment info.
This paging feature, unfortunately, highlights a major QA/testing issue. If you’re going to add paging support, any reasonable person would think you would make sure that older non-paging API’s continue to work. I see no possibility that this path could have been tested because it would have easily failed on your end. This, of course, assumes that the Exchange server used to test these API’s are also loaded down with plenty of data.
Regards,
Scott