SolutionXML not reading value correctly in Aspose.Diagram

Aspose.Diagram Product Family
1
Hello,

SolutionXML parts in a Visio document can contain a valid section of XML or just a text value.

When a Visio document is opened using Aspose.Diagram and a SolutionXML part just contains a text value then the XmlValue value is incorrect. It always returns the value "<>" for text values in SolutionXML parts.

It appears that your parsing of the SolutionXML parts is assuming that they will always contain a valid section of XML and it does not handle plain text values.

I have attached a zipped up Visio document with SolutionXML parts created using the Visio object model. This demonstrates the problem.

The SolutionXML parts are

5a6e6849-da31-4f27-89b1-7b78e3eedca5
]]>

The XmlValue for these SolutionXML parts obtained using Aspose.Diagram is always "<>" which is incorrect.

I see consistent behavior with all Visio file formats.

Duncan
2
Hi Duncan,

Thank you for your inquiry. We're working over your query and will get back to you soon.

3

Thank you Imran. Looking forward to your findings.


Regards
Duncan
4

Hi Duncan,


Thank you for being patient. We managed to replicate the incorrect XmlValue. This problem has been logged under ticket id DIAGRAMNET-50224 in our issue tracking system. Your request has also been linked to this issue. We’ll keep you informed regarding any available updates. We’re sorry for the inconvenience you faced.

5

Any news on when this will be addressed?

Regards
Duncan

6

Hi Duncan,


Thank you for the inquiry. We’re sorry to share with you that the linked issue id is pending for the analysis and not resolved yet. We have asked the responsible developer to take a look at your issue shortly. We’ll let you know once an update is available from him.

7

Hi Duncan,


Thank you for being patient. We have an update regarding issue id DIAGRAMNET-50224. We can only read SolutionXML part named as “docIndexRef”. So it is partially fixed. Our development team is in progress to fix this defect. Please spare us a little time. We’ll update you once it is marked as resolved.

8

Any more news on when the fix for this will be available?



Duncan

9

Hi Duncan,


Thank you for asking about an update. We’re sorry to share with you that it is in the analysis phase and not resolved yet. We have logged comment to provide an ETA. Please spare us a little time. We’ll let you know once a timeline is available.

10

This is now way beyond any acceptable definition of a “little time”. When will this be fixed?


You have had since September last year to address this but keep saying the same things while doing nothing. Actions will speak louder than your hollow empty words.

I am very disappointed with your service levels. You are happy to take our money but not make the product actually work. I ask again, when will this be fixed?

Duncan Smith
11

Hi Duncan,


Thank you for the inquiry. We’re in communication with our product team and will get back to you soon.

12

Hi Duncan,


Thank you for being patient. We have a good news for you that the issue id DIAGRAMNET-50224 has now been resolved. If there is no issue in the QA phase, then this fix will be included in the next version of Aspose.Diagram for .NET 5.5.0. It is expected in the first week of August, 2015. We’ll inform you via this forum thread as soon as the new release is published.

13

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

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

The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.