You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Ron Grabowski (JIRA)" <ji...@apache.org> on 2007/12/22 20:27:43 UTC
[jira] Resolved: (LOG4NET-78) Enhance AdoNetAppender to use ADO.NET
2.0 connectionStrings configuration element
[ https://issues.apache.org/jira/browse/LOG4NET-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Grabowski resolved LOG4NET-78.
----------------------------------
Resolution: Duplicate
Duplicate of LOG4NET-88.
> Enhance AdoNetAppender to use ADO.NET 2.0 connectionStrings configuration element
> ---------------------------------------------------------------------------------
>
> Key: LOG4NET-78
> URL: https://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.
-
You can reply to this email to add a comment to the issue online.