> I personally have not used the dotnet-commons-logging, so I don't know how > good/stable it is
I get a bad feeling when the only advertised documentation is "Release Notes" and even that link doesn't resolve, http://dotnetcommons.codeplex.com/Wiki/View.aspx?title=Release%20Notes&referringTitle=Logging. I am confident that the logging frameworks in .NET are not nearly as mature and various as those in Java. Commons logging emerged to address that diversity -- one API to rule them all. I would argue a .NET port of commons logging solves a non-existent problem. I believe we would be safe using either log4net or the built in trace capability, but as I said I believe the latter would be more foreign to anyone who has ever used a Java logging framework. M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
