https://github.com/sheryever/elmah.1x
Automatically exported from code.google.com/p/elmah.1x
https://github.com/sheryever/elmah.1x
Last synced: 3 months ago
JSON representation
Automatically exported from code.google.com/p/elmah.1x
- Host: GitHub
- URL: https://github.com/sheryever/elmah.1x
- Owner: sheryever
- License: apache-2.0
- Created: 2015-08-03T11:50:05.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2015-08-03T11:53:14.000Z (almost 10 years ago)
- Last Synced: 2025-01-11T06:16:28.932Z (5 months ago)
- Language: C#
- Size: 1.7 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.html
- License: COPYING.txt
Awesome Lists containing this project
README
ELMAH README
body
{
font-family: Arial, Helvetica, Sans-Serif;
font-size: small;
background-color: #fff;
}
p
{
margin-left: 80px;
}
h1
{
font-size: x-large;
}
h2
{
font-size: large;
}
h3
{
font-size: medium;
margin-left: 40px;
}
h4
{
font-size: small;
margin-left: 80px;
}
code, pre
{
font-family: Courier New, Courier, Monospace;
font-size: small;
}
li
{
padding-bottom: 0.5em;
}
ELMAH README
Please read this document carefully before using this release of ELMAH
as it contains important information.
For peer help and support, vists the ELMAH Discussion Group.
Report bugs and issues to the issue
tracker on the project site.
Avoid using the issue tracker to seek help with problems you are experiencing in
installing or running ELMAH. That is what the discussion group is for.
The best way to get started with ELMAH is to take it for a spin by launching
the supplied demo Web site. Simply go the root of your ELMAH distribution and
execute thedemo.cmd
script. The demo Web site requires
Microsoft .NET Framework 2.0.
Version 1.2 SP 2 Notes
TheSccStamp
class has breaking changes. ItsRevision
property is now typed asObject
instead ofInt32
.
ItsSortByRevision
method has been renamed toSortByLastChanged
These change should have practically no impact on existing installations as
SccStamp
is not considered an integral part of the ELMAH public
API. It is intended to be used by ELMAH itself for informational purposes
and support diagnostics.
Version 1.0 BETA 3 Notes
Upgrading from ELMAH 1.0 BETA 2(a)
Microsoft SQL Server Error Log
If you are using Microsoft SQL Server (2000 or later) for your error log then you should re-create
the stored procedures found in the supplied SQL script (seeSQLServer.sql
).
The script does not contain DDLDROP
orALTER
statements so
you will have to drop the stored procedures manually before applying the
CREATE PROCEDURE
parts of the script. Other than that, there have been no
changes to the schema since BETA 2a so existing data in your logs can be left as it is.
Oracle Error Log
The Oracle error log is new in BETA 3, but if you have been compiling ELMAH
from sources between BETA 2 and 3 and using Oracle for your error log then you should re-create
theELMAH$Error
table, its indicies and related packages using the
supplied SQL script (seeOracle.sql
in your distribution). The script
does not contain anyDROP
statements so you will have to drop the
table and package manually before applying the script. If you wish
to preserve the logged error data, you should consider archiving it in
a backup. Please read the comments in this script file carefully for
hints on users and synonyms. NB The original package has now been split in two to aid in
securing the database in enterprise scenarios.
VistaDB Error Log
The VistaDB error log is new in BETA 3, but if you have been compiling
ELMAH from sources between BETA 2 and 3 and using VistaDB for your
error log then you should delete the.vdb3
file and allow it to be
re-created.
Microsoft Access Error Log
The Access error log is new in BETA 3, but if you have been compiling
ELMAH from sources between BETA 2 and 3 and using Access for your
error log then you should delete the.mdb
file and allow it to be
re-created.
Version 1.0 BETA 2(a) Notes
Upgrading from GDN-ELMAH or ELMAH 1.0 BETA 1
The configuration sections and entries have changed slightly if you are
using GDN-ELMAH, which is the original that was released on GotDotNet.
Consult thesamples/web.config
file to see examples of
how the configuration looks like now.
If you are using the Microsoft SQL Server for your error log then you should re-create
theELMAH_Error
table, its indicies and related stored procedures
using the supplied SQL script (seeDatabase.sql
in your distribution).
The script does not contain DDLDROP
statements so you will have to drop
the table and stored procedures manually before applying the script. If you wish to
preserve the logged error data, you should consider archiving it in a backup.
$Revision$