Issue Tracker for the commercial versions of ServiceStack
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
README.md Update README.md Jul 24, 2018

README.md

ServiceStack Issues

This is the Issue Tracker for commercial customers of ServiceStack only. Please register your email or GitHub username at https://servicestack.net/account/support before reporting any issues. Only .NET Core 2.1 is supported on non-Windows platforms. The list of supported ServiceStack packages are on the download page and NuGet.

This Issue tracker is for reporting reproducible bugs/issues only. Please refer to your account support page for your available support options, e.g. You can use the Customer Forums or StackOverflow for any technical support questions or use ServiceStack's UserVoice to submit any feature requests.

You can view existing issues or report a new issue.

Each issue must be reproducible with either a failing test, sample code, gist, link to a stand-alone project or otherwise clear steps to reproduce the issue. For details please see How to create a Minimal, Complete, and Verifiable example.

How to create a good Bug Report?

If your bug report is effective, chances are higher that it will get fixed. So fixing a bug depends on how effectively it's reported.

1) Reproducible:

If your bug is not reproducible it will never get fixed. You should clearly provide the steps to reproduce the bug. Do not assume or skip any reproducing step. A Step-by-step description of the issue is easy to reproduce and fix. E.g. A failing test with the issue (or in a gist) is the preferred way to report a reproducible error as it contains all the assumptions and environment settings necessary for the error to occur.

2) Be Specific:

Do not write a essay about the problem. Be Specific and to the point. Try to summarize the problem in minimum words yet in effective way. Do not combine multiple problems even they seem to be similar. Write different reports for each problem.

3) Environment Details:

Include the product and version of ServiceStack you're using, the Operating System and the versions of the relevant major components, e.g. What .NET version, IIS Version, SQL Server version (if it's issue with OrmLite), etc.