Using log4net and/or log4cxx in mixed systems

[CD]

Hello All,

We have some legacy logging infrastructure, which I would like to
replace with log4net. However, many subsystems are written in C++.

I can see some options here:
(1) Use log4net and write a C++ facade to it, which would be used by
the C++ applications. To me this is the easiest solution but I am
concerned with the performance when logging from the C++
applications.
(2) Use log4cxx and write a wrapper from C#. This is more complicated
to me because I have a custom appender calling a WCF service in
another box for persistence.
(3) use both. This would imply a lot of repeated code and
maintenance.

Did I miss anything?

I would appreciate your comments and suggestions.

Kind regards
CD

 

[Arne Vajhøj]

We have some legacy logging infrastructure, which I would like to
replace with log4net. However, many subsystems are written in C++.

I can see some options here:
(1) Use log4net and write a C++ facade to it, which would be used by
the C++ applications. To me this is the easiest solution but I am
concerned with the performance when logging from the C++
applications.
(2) Use log4cxx and write a wrapper from C#. This is more complicated
to me because I have a custom appender calling a WCF service in
another box for persistence.
(3) use both. This would imply a lot of repeated code and
maintenance.

Did I miss anything?

I would go for #1, because of the argument in #2.

It cost a little bit to switch between managed and
unmanaged, but if you are using an appender that calls
a WCF service to persist on a remote node, then I don't
think you should worry about it - it will be insignificant
compared to the time spend in that appender.

Arne