We experience an issue with the SVG generation from xlsx charts. Depending on the target framework the .svg file will be slightly different. This difference is enough to break functionality in other libraries when trying to use the svg file, including Aspose.Imaging when trying to convert it to a bmp file. The difference is also visual when looking at the two files.
<TargetFrameworks>net6.0</TargetFrameworks> => net6.0 target works - and file can be rendered/ converted correctly
<TargetFrameworks>net6.0-windows</TargetFrameworks> => net6.0-windows target does not work - and file can not be converted/rendered correctly
<TargetFrameworks>net48;net6.0-windows</TargetFrameworks> => net6.0-windows + net48 target does not work - and the file can not imported/rendered correctly
@licenselogimatic
We generated files under the frameworks net6.0 (Skiasharp) / net4 / net6-windows for comparison. Indeed, as you mentioned, there are differences in the generated files, as AsposeSVG.zip (40.1 KB)
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): CELLSNET-57128
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
For the issues of differentiation, we have optimized the results as follows, which will take effect in version 24.11. CELLSNET-57128_241106.zip (61.3 KB)
The issues you have found earlier (filed as CELLSNET-57128) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi