Automatic bug reporting

[Ariel Raunstien]

Hey gang.

It's sometimes possible for your application to automatically create an issue (bug, defect) when it identifies a failure.

I'm about to implement such a mechanism (Log4Net+FogBugz+BugzScoutAppender) and was wondering if you have any tips (technical or otherwise).

Arielr

http://blogs.microsoft.co.il/blogs/ariel/

[Dotan N.]

look at hoptoad

--

You received this message because you are subscribed to the Google Groups "altnetisrael" group.
To post to this group, send email to altnet...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/altnetisrael?hl=.

[Ariel Raunstien]

Web oriented; I'm desktop.

It looks cool, though.

Arielr

http://blogs.microsoft.co.il/blogs/ariel/

[Dotan N.]

i meant that you can look at some of the ideas. shouldn't be that different. coincidentally this weekend i've planned on doing something in the form of what you're trying to do.

however, time constraints push it further away from me =\

[Ariel Raunstien]

Ah.

The biggest web-desk difference in implementations for me is the network access - in a web solution there's no harm in pinging another server with a bit of data; with a desktop solution - I don't want to bother the network all the time (Resharper's error reporting springs to mind).

That means that "issue merges" should be done client side; which means I need to store "previous errors" and send a batch periodically (or on command); which means a naive log4Net appender isn't the right tool for the job.

Unless this custom appender will start a thread to poll a directory for new outgoing messages... (and that doesn't sound right) 

Arielr

http://blogs.microsoft.co.il/blogs/ariel/