This project has moved and is read-only. For the latest updates, please go here.

Joins Reporter projects

Jan 29, 2013 at 11:46 AM
Edited Jan 29, 2013 at 11:46 AM

Why not join in one project: Exception Reporter and CrashReporter.Net ?

Jul 1, 2013 at 3:49 AM
Edited Sep 10, 2014 at 3:55 PM
Thanks for the suggestion,

The CrashReporter.NET seems to have been copied from ExceptionReporter... I'm not sure any joining would be worth it.

One example is, the code in CrashReport.NET for CaptureScreenshot has obviously been copied from a very old source, as it uses raw win32 API's to get the job done -

It doesn't cater for multiple monitors either. In fact, it will probably capture the "wrong" monitor if you have more than one.

Compare this to our ScreenshotTaker -
Which captures all monitors and in about half the code.

I would simply keep all our code & delete all of the other. And that seems to be the better decision in other cases I can see, from a quick browse-through.

*EDIT - as discussed in the CrashReport.NET thread, my comment about being copied was wrong (sorry to CrashReport.NET). But in summary, this project is a cut-down, simplified version of what ExceptionReporter does and has no potential for merging. In my opinion, the cut-down of features and code offers no benefit that I can appreciate - so I would/could not use anything CrashReporter.NET has.
Jul 1, 2013 at 6:46 AM
Edited Jul 1, 2013 at 6:47 AM
I'm not sure about whatt you're saying. I honestly appreciate the effort put by SimonCropp and you in Exception Reporter but believe me i didn't use any of the code from the Exception Reporter project. I just used your interface design ideas. Surely i can give you credits for interface design ideas you put in Exception Reporter. I got the screen capture code from stack overflow.
Jul 1, 2013 at 7:10 AM
Thanks, good question about it.

Finally, not CrashReporter.NET has been copied from ExceptionReporter?

Anyways, I honestly appreciate the effort for both projects.

For a newbie programmer, better is only project about it, using good patterns. Join efforts and share with community.

Better code and good patterns in Exception Reporter project, isn't?
Jul 1, 2013 at 7:23 AM
I'll keep this discussion in the CrashReporter.NET thread to avoid duplication.