Consequences of 3.0.3 using MS Logging

[jjomda]

I notice that there is a new Spring release and it uses MS Logging. Is there any documentation about that change? I didn't find it.

We have an application that uses Common.Logging (mostly due to Spring.Net already using it) & log4net. I haven't played around with 3.0.3 but I see lots of build errors for the projects that referred to Spring.Net with version number "3.*". Maybe that wasn't a good idea. I've hardcoded those to 3.0.2 for the time being.

But going forward we probably want to go to the latest version. What do we need to do regarding logging? Can we continue using Common.Logging while retaining the logging happening inside Spring? If not what are our options?

Regards,
Jan-Jaap

[lahma]

You can continue using 3.0.2 if you don't want to switch to new logging abstraction. Spring.NET is in maintenance mode so you won't be missing much. New MS Logging allows more idiomatic usage in NET land and opens more logging solutions to be used. Common.Logging is no longer maintained.