Shapes change form when converting a .vsdx to .vdx

Hi,


We have a .vsdx process file created with Visio 2013 which contains a number of shapes.

We do the following:
- Open the file using Aspose.Diagram 6.0
- Save it as .vdx using Aspose.Diagram 6.0
- Open the .vdx created with Aspose.Diagram using Visio 2013

Some shapes have changed!

When we save the .vsdx to .vsd using Visio 2013, and then convert the .vsd to .vdx using Aspose.Diagram, the resulting .vdx has the correct shapes.

I included both the .vsd and .vsdx we convert to .vdx using Aspose.Diagram. I also included a screenshot with the wrong and correct results.

Can you also reproduce this issue?

Best regards,
Robert Wielink
Infoland BV

Hi Robert,


Thank you for the details. We have evaluated your sample Visio against the latest version 6.0.0 of the Aspose.Diagram API and figured out how to duplicate the said issue. We’ve logged this problem under ticket id DIAGRAMNET-50694 in our bug tracking system. Your post has also been linked to this ticket. We’ll keep you informed regarding any available updates. We’re sorry for the inconvenience caused.

Hi Robert,

Thank you for being patient. We have a good news for you that the issue id DIAGRAMNET-50694 has now been resolved. If there is no issue in the QA phase, then this fix will be incorporated in the next version 6.2.0 of the Aspose.Diagram for .NET API. We'll inform you via this forum thread as soon as the new release is published.

Hi Robert,


Thank you for being patient. In reference to the ticket id DIAGRAMNET-50694, please download and use the latest Hotfix version: Aspose.Diagram for .NET 6.1.1.0. Please also let us know how that goes on your side.

Hi,


This seems to work.
Thanks for the update.

Regards,
Robert Wielink
Infoland BV
Hi Robert,

Thank you for the confirmation. It is nice to hear from you that the problem has been resolved. Please let us know if you require any further assistance, we will be happy to help you.

The issues you have found earlier (filed as DIAGRAMNET-50694) have been fixed in Aspose.Diagram for .NET 6.2.0.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.