We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Daily recurrence time is getting changed in appointment

Hello Team,

I’ve been using Aspose.Email to create appointment in .pst(Microsoft Outlook) file.

I am trying to set daily recurrence in the appointment by providing date time but some how its getting changed after exporting.

I’ve written every explanation in the code once you see the code in the attachment.

I’m using Aspose.Email, i know this issue is solved using the same code in your latest version

But its very very hard to change the code as latest api required some namespace changes and we can’t redeploy using latest version and its a very huge change and critical for us.

Can you please escalate this issue to your higher authority and cause we are losing money and our project and our company will get shutdown due to that.

I am requesting you that is it possible to solve this issue in version as we have already purchased your API but can’t upgrade and redeploy.

So can you please escalate this issue to higher authority and take it on high-priority please.

Looking for positive response.

Thank You.


Hi Amit,

We regret the inconvenience caused to you. However, we can not be of much help to you in this regard as we don’t fix issues in older versions. This is as according to our quality policy where we only fix issues that are reproducible with the latest version of the API. Moreover, fixing such issue can lead to other potential problems that would have been, otherwise, dealt in our routine monthly releases. So, its not practical for us to fix an issue with an older version and provide the fixed version. We hope you understand our point of view in this regard.

PS: Upgrading to the latest version of the API do have changes related to restructured namespaces. However, upgrading to this restructure namespace of the API is completely [documented](https://docs.aspose.com/display/emailnet/Aspose.Email+for+.NET+16.12.0+(Revamped)+Release+Notes) and can be followed to cater for this change in the API namespace structure.