CLI tips

• .NET runtime check: dotnet --list-runtimes
• GemBox .NET component version: dotnet list package
• If you need GemBox API details, look them up locally in the XML docs. Example GemBox.Spreadsheet NuGet paths:
  • Linux/macOS: ~/.nuget/packages/gembox.spreadsheet/2025.12.105/lib/*/GemBox.Spreadsheet.xml
  • PowerShell: $env:USERPROFILE\.nuget\packages\gembox.spreadsheet\2025.12.105\lib\*\GemBox.Spreadsheet.xml
• Use ripgrep to search the XML. E.g.:
  • Linux/macOS: rg -n "Autofit" ~/.nuget/packages/gembox.spreadsheet/2025.12.105/lib/**/GemBox.Spreadsheet.xml
• If the API is unclear, scan namespaces and remarks/examples in the doc XML before coding. E.g.:
  • Linux/macOS: rg -n "namespace GemBox|Drawing|PivotTables" ~/.nuget/packages/gembox.spreadsheet/2025.12.105/lib/**/GemBox.Spreadsheet.xml

Online search

If you don't find relevant docs via CLI, and you have network access, search online:

1. Open a relevant official example page, as examples listed below provide the most information. E.g, if you need custom fonts in GemBox.Document, the base URL is "https://www.gemboxsoftware.com/document/examples/". The specific example that mentions fonts is "fonts/103", so open "https://www.gemboxsoftware.com/document/examples/fonts/103" page.
2. If examples are insufficient, search the official API documentation of a specific component. E.g. GemBox.Spreadsheet online search filter: "site:https://www.gemboxsoftware.com/spreadsheet/docs"

Validation

Once you are finished, validate the code by compiling the project. If there are errors related to GemBox API usage, modify the code accordingly. Ignore compilation errors that are not related to GemBox or not caused by your edits.