ELMAH Google Group

Re: Hoptoad Module

2010-01-06T20:33:08Z

There's also a Google Group for the development of Hoptoad notifier
plugins:
[link]
Drop by if you have any questions or issues integrating with Hoptoad.
Cheers,
Jason Morrison
thoughtbot

Re: Hoptoad Module

2010-01-06T20:21:45Z

There are other .NET developers using Hoptoad and at least one other
known open source .NET project but it also uses an old version of the
API:
[link]
If you'd like to write your own, the new XML API is documented at:
[link]

Re: [ELMAH] Hoptoad Module

2010-01-06T19:57:26Z

This is certainly a nice integration to have. I gave Hoptoad a spin some
time ago but your message prompted to look at it again and it's certainly
come a long way. I think you could start lightly by sharing your solution as
an attachment to a post in the group when you're ready for initial feedback.

Hoptoad Module

2010-01-06T15:29:56Z

Hi everyone,
I've written the start of a module that sends exceptions logged by
ELMAH to a web application called Hoptoad ([link]
home), and I was wondering if I should put the code out there once I
whip it into shape.
A few questions:
-Should I even do this? I have no idea if any .NET devs are even using

Re: [ELMAH] ELMAH on top of an existing application which has an error handling mechanism

2010-01-05T23:38:02Z

Just don't register the ErrorMailModule from ELMAH in your configuration
file and it will never send mails for unhandled exceptions. You can still
continue to use the logging and viewing facilities of ELMAH because those
are enabled through registration of independent an independent module and
handler.

Re: [ELMAH] Anyone know how to filter this exception?

2010-01-05T23:35:02Z

Have you checked the following thread also related to filtering
CryptographicException?
[link]
The thread was inconclusive but do any of the examples help in your case?
- Atif

Re: [ELMAH] Custom Error Page

2010-01-05T23:30:32Z

This is something you need to develop yourself. ELMAH's
*ErrorLogModule* provides
a *Logged* event that you can handle in *Global.asax* and which you can use
to communicate details, say via *HttpContext.Items* collection, to your
custom error page. If you registered the *ErrorLogModule* under the name *

Re: [ELMAH] Differences in functionality between production and development servers

2010-01-05T23:23:01Z

That's correct.
Deploying a PDB to a release build should be perfectly safe if you've taken
all other precautions that are the usual suspects in securing a production
web server and ASP.NET box . Can you cite any online and authoritative
references that discourage deploying PDB in production? Meanwhile, you may

Re: Handler working, Modules not

2010-01-05T14:57:58Z

Problem solved - I had to add "<clear />" at the top of the
httpmodules list.

Re: Handler working, Modules not

2010-01-05T14:32:26Z

Correction - on development, the configuration is at the root of the
website. On production it is at the virtual directory level. Do I
need to configure something related to the "application" column (in
elmah_error)?

Re: Handler working, Modules not

2010-01-05T14:05:01Z

I should also note that this is the configuration of a virtual
directory ([link]), not the top level web-
site. However, that is also the case on development.

Re: Handler working, Modules not

2010-01-05T14:02:21Z

Thanks James,
1) Yes, this works
2) Exception generated, not logged in table, doesn't appear in axd.
Good point on the writing - I should've noted that the app can write
data as well using the existing connection string. I also ran the
"elmah_logerror" sproc in ssms with the same credentials and was able

Re: ELMAH and subdomains

2010-01-05T00:48:08Z

Hi Sean,
Don't think there should be a problem. Each of the subdomains *may*
need to be configured separately for ELMAH (quite possibly/probably
with exactly the same config).
Have you got the ELMAH handler working?
If not, and even if you don't intend to use it, get this up and
running.
It will show you which error log you are using (bottom of the screen).

Re: Handler working, Modules not

2010-01-05T00:41:42Z

Hi Jeremy,
You say that the handler is working OK... in which case, can you do
the following:
1) Open elmah.axd and have a look at the bottom of the page. It should
say something like "This log is provided by the Microsoft SQL Server
Error Log." which should tell you if you've got the correct error log

Handler working, Modules not

2010-01-04T22:29:36Z

I have installed and configured Elmah. In a dev environment, the
handlers and modules both work as expected. The handler (i.e.
elmah.axd) is working fine on production, but the modules appear to be
failing (no sql log, no email). Any pointers to troubleshoot?
The config is simply copied from dev to prod, and the connection