Stuck? Here's how to get unstuck
All support is public and free, and happens on GitHub — searchable answers help the next person with the same question.
1. Check the documentation first
Most questions are answered in the guides, which are versioned with the code:
- PDF Reporting docs — layout, text, encryption, barcodes, vector graphics.
- HTML Reporting docs — including a FAQ & troubleshooting page and a cookbook of recipes.
- DOCX Reporting docs — including a dedicated troubleshooting page.
- Samples — rendered output with a link to the C# source of every document.
2. Search existing issues
Someone may have already hit your problem. Each library has its own issue tracker — search closed issues too:
- TerraFluent.Pdf.Reporting issues
- TerraFluent.Html.Reporting issues
- TerraFluent.Docx.Reporting issues
3. Open an issue
Found a bug, or need a feature? Open an issue on the repository of the package you're using. The most useful reports include:
- The package name and version (e.g.
TerraFluent.Pdf.Reporting 2.0.2). - Your target framework and OS (e.g. .NET 8 on Linux/Docker).
- A minimal, runnable code snippet that reproduces the problem.
- What you expected, and what actually happened — attach the generated file if the problem is in the output.
What to expect
TerraFluent is free, MIT-licensed open source, maintained on a best-effort basis — there is no paid tier and no SLA. Well-written bug reports with a minimal repro are typically the fastest to get fixed. Security issues follow a separate, private process — see the security policy.
Evaluating TerraFluent for your organisation? The enterprise page collects the answers reviewers usually need: licensing, dependencies, release policy, and security posture.