mstodd / elmah

Automatically exported from code.google.com/p/elmah
Apache License 2.0
0 stars 0 forks source link

Intellisense for web.config and external config files #239

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Adding intellisense support when configuring Elmah using web.config would help 
new users.  It would also make it easier to adjust the settings without having 
to check the documentation.  Trickier elements such as error filtering would 
also be a bit easier to understand.

I have attached an xml schema definition (xsd) file that provides basic 
intellisense in visual studio.  This is the first xsd that I have created so 
perhaps somebody else can clean this up.  One limitation I am aware of is that 
custom errorFilter assertions won't validate.

To use this file place it anywhere in your project, then add the following 
attribute to the elmah element:

<elmah xmlns="http://Elmah.Configuration">
</elmah>

If you use external configuration files just add the above attribute to the 
root element of the file.

The namespace I used in the xsd is "http://Elmah.Configuration" but feel free 
to change that to whatever you wish.

Original issue reported on code.google.com by JeffLin...@gmail.com on 13 Jul 2011 at 2:28

GoogleCodeExporter commented 9 years ago
Oops, forgot to actually attach the file.

Original comment by JeffLin...@gmail.com on 13 Jul 2011 at 2:30

Attachments:

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
in the errorLogCT you are missing entries for the attributes 
connectionStringName and providerName, see my update file attached (lines 47 & 
48).

thanks

Original comment by davidada...@googlemail.com on 21 Nov 2014 at 7:00

Attachments:

GoogleCodeExporter commented 9 years ago
This issue has been migrated to:
https://github.com/elmah/Elmah/issues/239
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is 
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of 
any further development.

Original comment by azizatif on 25 Aug 2015 at 8:21