views:

1539

answers:

5

Does anyone know of a good crash reporting library for C#?

In C++ there is CrashRpt available, so I'd like something along those lines.

Ideally I'd like the library to zip up general information about the computer, and a crash mini dump file.

I would also need a library that is free for commercial use and that has source code available.

+3  A: 

In response to requests for a port of CrashRpt, its author has suggested calling the unmanaged DLL from C#. Maybe this is an option for you...

David Crow
+4  A: 

Have a look at these: SmartInspect: http://www.gurock.com/products/smartinspect/ SmartAssembly: nhttp://www.smartassembly.com/

Conrad
+1  A: 

From my Delphi-times, I have had a very good experience using EurekaLog, of which a .NET version has been released recently:

http://www.eurekalog.com/

I've only ever tried the delphi version though, so I can't say anything about the .NET one. The tool is very powerful in what it does though (it can even submit crash reports directly into many common bug tracking systems) and it's very easy to set up and use.

It does come with source code, but it's not free. It's royalty free though. And not that expensive considering the feature set.

pilif
+8  A: 

Try out:

1) Exception Reporter

http://www.codeplex.com/ExceptionReporter


2) Bug Trap

http://www.codeproject.com/KB/applications/BugTrap.aspx

BugTrap's author site:

http://www.intellesoft.net/downloads.php

BugTrap comes with BugTrapN.dll for .NET managed support.


3) BugzScout

Also, if you use FogBugz, try BugzScout:

http://support.fogcreek.com/default.asp?W741


These are free and come with source (except BugzScout unless you're using their 2 user startup edition).

Brian Chavez
http://www.codeplex.com/ExceptionReporter is Great !!Thanks Brian. Exactly what I was looking for.
gpgemini
+2  A: 

Sign up for WinQual and let Microsoft handle all of the leg work for you.

(you'll need IE to click on the WinQual link)

Roger Lipscombe
If you're going to downvote; at least leave a comment. What's wrong with using WinQual? We use it and, while the uptime on Microsoft's end isn't great, we're having great success with it. We've got in-house tools that periodically download WinQual reports (and crash dumps) into our bug database. It's working pretty well for us.
Roger Lipscombe
Good answer, why re-invent the wheel.
Filip Ekberg
Winqual is good - only problem I can see is the delayed reporting. t takes some time to get information, but not a big deal.
Tim