Client Library Development Guidelines

We're looking for enthusiastic developers to build out API client libraries in various technologies. If you're up to the task of putting together a functioning wrapper of the Regressor.NET API in your language of choice, we'll be more than happy to hook you up with a Free Lifetime Subscription to Regressor.NET.

Guidelines

In general, you should follow the pattern set out by our flagship ASP.NET Client Library. Here are a few things it should do:

• Drop into a project with the minimum disruption. So don't go building anything that requires modifying every single file, or a monumental framework that people have to plug their project into.
• Do its thing automatically by inserting itself somewhere in the global error handling chain in the technology in question. End users should not have to write any code to capture errors and submit them to the API.
• Don't break anything. Look, this is a tool that's supposed to make things better, not worse. Your code will only get called if something has already gone wrong, so don't make any assumptions that the environment will be in a stable place. Wrap everything in a giant try/catch and simply eat any exception that might try to escape.

  Reporting errors is about as low priority as you can get. The last thing you want to do is divert an end user away from the developer's pretty error screen to show him a stack trace.