Support policy

Support is part of a paid license, and it is by email. This page gives the response target for each edition, which IntentSharp versions receive fixes, which .NET versions they run on, and how to report a bug or a security problem.

Response targets by edition

Edition	Support
Developer	Email, 2 business days
Business	Priority email, 1 business day, plus a named contact
Enterprise	Priority email, 1 business day, plus a named contact
OEM / redistribution	Priority

Existing Team licenses continue, with the support they were bought with.

These are targets for our first answer, not a promise that a problem is fixed within that time. A business day is a weekday in the US Eastern time zone, excluding US federal holidays, and support is answered during US Eastern business hours.

Note

Subject to change. When we are away for more than two business days, an automatic reply says when we will answer, and targets count from then.

A lapsed license has no support. It keeps the right to use the releases its last key covers (see Licensing).

Supported versions

Note

Subject to change.

• Fixes are made on the latest minor release of the current major version. To receive a fix, upgrade to the release that contains it.
• When a new major version is released, the previous major version receives security fixes for 12 months.

IntentSharp 1 is the first major version; there is no earlier one.

.NET versions

The packages target .NET 8, .NET 9 and .NET 10. Which .NET versions IntentSharp supports follows Microsoft's support dates for .NET.

Note

Subject to change. Microsoft's support for .NET 8 and .NET 9 ends on 10 November 2026. After that date, fixes are made and tested on supported runtimes; an older target stays in the packages until a release removes it, announced in the changelog.

Report a bug

Write to licensing@c2consultants.net. Include:

• the IntentSharp version and the .NET version;
• the license id, which starts with lic_ (you do not need to send the key);
• what you did, what you expected and what happened, with the exception or log lines;
• the smallest code that shows the problem, if you can.

Do not include API keys, connection strings or personal data. There is no public issue tracker or forum; reports come to us by email.

Report a security problem

Do not report a security problem in public. Security says how to report one and what to include; the contact is also published in security.txt.