Introducing OneTrueError.com

OneTrueError.com is my new startup for .NET developers. It’s a bit like ELMAH, but for most of Microsoft’s different frameworks, and with a tad bit of analytics.

As you might have noticed I’ve not been blogging that much the last year. And that’s basically because that I’ve tired of all log files that you have to wade through to know if you have any unexpected problems. And when you finally find errors, you have to try to build a context to be able to reproduce the error.

Wouldn’t it be great if you just could configure errors with two lines of code:

OneTrue.Configuration.AddSubmitter(
    new ReportToOneTrueError(
        "e5fccaff-f364-4c41-8c2b-783df78e7991",
        "86496810-af50-42a0-b2ff-f6b1558c3cd7")
    );
OneTrue.Configuration.CatchAspNetExceptions();

So that if an exception occurs in your code:

[HttpPost]
public ActionResult SendMessage(SendMessageViewModel model)
{
    if (!ModelState.IsValid)
        return View(model);

    var repos = new MessageRepository();
    repos.Send(model);

    return RedirectToAction("Index");
}

You’ll get an error page (which has different predefined configurations and you can easily customize it):

error

And at the same time you can see loaded assemblies, the posted data, the exception etc in a web site:

reportinfo

Now you can.

The service will also detect duplicates so that you only get one incident, even if the exception is thrown ten or ten thousand times.

duplicates

The service is currently an open beta and will be so for two months. The service should be stable but some features are still missing before the stable release.

All beta users will get the “basic” plan for free for one year when the service goes out of beta in a month or two.

Signup for my new service at onetrueerror.com