Our code creates Excel hyperlinks on a "Contents" sheet using this method:
public void SetHyperlinkSheetCell(int row, int col, string linkText, int indexSheet)
{
string sheetName = workbook.Worksheets[indexSheet].Name;
if (sheetName.Contains(' '))
sheetName = "'" + sheetName + "'";
string docLink = sheetName + "!A9";
int indexLink = worksheet.Hyperlinks.Add(row, col, 1, 1, docLink);
Hyperlink hyperlink = worksheet.Hyperlinks[indexLink];
hyperlink.TextToDisplay = linkText;
hyperlink.ScreenTip = "View worksheet " + sheetName;
}
This worked fine in Excel and also when saving to Aspose.Cells.FileFormatType.Pdf before we switched to Aspose.Cells.NET version 4.9.0.5. Since switching to 4.9.0.5 the links no longer work in the pdf file format. Is this a bug or has something changed in the usage of hyperlinks?
Hi,
After an initial test, I found the issue. We will figure it out soon.
Your issue has been logged into our issue tracking system with an issue id: CELLSNET-16611.
Thank you.
Hi,
We have fixed your mentioned issue, kindly try the attached version.
Thank you.
The issues you have found earlier (filed as 16611) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
While trying to keep the API as straightforward and clear as possible, we have decided to recognize and honor the common development practices of the platform; we have re-arranged API Structure/ Namespaces.
With this release, we have reorganized the API classes for Aspose.Cells component. This change has some major aspects that we follow. We have added new namespaces. The entire API (classes, interfaces, enumerations, structures etc.) were previously located in the Aspose.Cells namespace. Now, certain sets of API have been moved to their relative namespaces, which make the relationship of classes (with their members) and namespaces clear and simplified. It is to be noted here, we have not renamed existing API (classes, enumerations etc.) but, I am afraid you still need to make certain adjustments in your existing projects accordingly.
For complete reference, please see the product's API Reference.