What steps will reproduce the problem?
1. Setup ELMAH on a web site
2. Configure it to use the VistaDBErrorLog
3. Do not specify the connection string or leave it empty.
What is the expected output? What do you see instead?
One would expect a specific error along the lines of, "Connection string
is missing." Instead, in a DEBUG build, one gets the assertion attached in
assert.txt. Ignoring the assertion leads to the following exception
attached in error.txt. In a RELEASE build, only the exception attached in
error.txt occurs.
Additional information:
Here is how the ELMAH configuration section looked like:
<elmah>
<errorLog type="Elmah.VistaDBErrorLog, Elmah" />
</elmah>
The same happens if you have the following:
<elmah>
<errorLog type="Elmah.VistaDBErrorLog, Elmah" connectionString="" />
</elmah>
Environment:
- ELMAH version: revision 326 of the source repository
- OS: Windows Vista Business Edition SP 1 (Build 6001)
- ASP.NET: version 2.0
Original issue reported on code.google.com by azizatif on 12 Jun 2008 at 12:17
Original issue reported on code.google.com by
azizatif
on 12 Jun 2008 at 12:17Attachments: