|
1
1
|
Before I reinvent the wheel, I wanted to ensure that this doesn't exist already somewhere. I want to take any errors thrown by ASP.NET, and rather than display them to the user, I want to capture them into FogBugz (potentially using BugzScout) and then display a custom friendly error message to the user with the new ticket number. Does something like this already exist? |
|||
|
|
|
1
|
You'll have to do a little work on your end, but that is pretty much what the api is for. Take a look at the docs for guidance on how to set it up. I have this running on a bunch of apps where I work, but sadly not in .net. I don't know for sure that the ixBug is returned with cmd=new. I didn't implement that. One part that I do find maddening is that you can't put html in the body of your bug. I have a nicely contained css/javascript based error message that is much easier to read than the plain text error dump I'm using. Good Luck! |
||
|
|
|
0
|
To add to Mike's answer, you can take a look at how FogBugz itself uses a custom error page to send exceptions to BugzScout by looking at |
||
|
|
