[ http://issues.apache.org/jira/browse/LOG4NET-78?page=comments#action_12426375 ] Phil Haack commented on LOG4NET-78: -----------------------------------
I would like to second this issue and note that you might consider "connectionStringName" as the name of the element as that is the name used by the provider model such as the MembershipProvider. I only suggest this because many developers will already be familiar with the meaning of "connectionStringName" as being a property that references a value in the <ConnectionStrings> section. Thanks! > Enhance AdoNetAppender to use ADO.NET 2.0 connectionStrings configuration > element > --------------------------------------------------------------------------------- > > Key: LOG4NET-78 > URL: http://issues.apache.org/jira/browse/LOG4NET-78 > Project: Log4net > Issue Type: Improvement > Components: Appenders > Affects Versions: 1.2.9 > Environment: Windows XP > Reporter: JocularJoe > > .NET 2.0 has a <connectionStrings> element in the application configuration > file. > This makes it convenient to manage all connection strings in one place. > It would be nice to enhance AdoNetAppender to be able to use a connection > string defined in the <connectionStrings> element > For example, add a new element <connectionStringRef> element to the > <appender> configuration which references the name of a connection string > defined in the <connectionStrings> element of the application configuration > file. This could be used instead of the existing <connectionType> and > <connectionString> elements. > Advantage: connection strings are managed in one place and can take advantage > of .NET 2.0 encrypted configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
