[
https://issues.apache.org/jira/browse/DMAP-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Werner Keil updated DMAP-152:
-----------------------------
Summary: Use Log4net to log in .NET clients (was: Use log4net to log in
.NET clients)
> Use Log4net to log in .NET clients
> ----------------------------------
>
> Key: DMAP-152
> URL: https://issues.apache.org/jira/browse/DMAP-152
> Project: DeviceMap
> Issue Type: Improvement
> Components: .NET API
> Environment: Windows
> Reporter: Werner Keil
> Assignee: eberhard speer
> Priority: Minor
> Labels: .net, Windows, log4net, logging
>
> Currently the .NET clients have a very simple logging abstraction only
> writing to the console. While it would add one external dependency (of
> another Apache project ;-) ) using *Log4net* in these places could improve
> flexibility and control of logging, e.g. log into both files and the console,
> tweak log levels, etc.
> I evaluated .NET logging for a client project and did not find a satisfying
> built-in log API similar to at least *java.util.logging* on the Java side. If
> it exists, please advise. Since our solution here has to combine .NET and
> Java apps working together in a larger system Log4net and Log4J were a pretty
> natural choice. Unless Microsoft has something out of the box in .NET this
> being an Apache project would also make the license topic a no-brainer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
