ELMAH 1.x shipped with a number of ErrorLog implementations built-in. This had the simplicity and advantage of shipping and deploying a single assembly in production. However, it required everything to be managed and released as a single unit and this made coordinating between the various ErrorLog authors/contributors difficult. Moreover some of the authors don't appear to be actively maintaining their implementations anymore. Going forward, the ErrorLog implementations will be split into separate repositories so that each can have its own issue tracking, release management, evolution and ownership.
ELMAH 1.x shipped with a number of
ErrorLog
implementations built-in. This had the simplicity and advantage of shipping and deploying a single assembly in production. However, it required everything to be managed and released as a single unit and this made coordinating between the variousErrorLog
authors/contributors difficult. Moreover some of the authors don't appear to be actively maintaining their implementations anymore. Going forward, theErrorLog
implementations will be split into separate repositories so that each can have its own issue tracking, release management, evolution and ownership.