You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Common.Logging 3.4.1 NuGet package supports .NET 3.5 and .NET 4.0 but Common.Logging.Core 3.4.1 only supports .NET 4.0.
So, no there's no support for .NET 2.0 in the NuGet packages and if I target .NET 3.5 in my project then NuGet still fails to install the version 3.4.1 packages because even though Common.Logging supports .NET 3.5 it depends on Common.Logging.Core which does not.
I can download the source code and build the .NET 2.0 assemblies but as Common.Net.snk isn't available I have to sign them using my own key. I can live with this but it's not ideal.
It would be good if the .NET 2.0 assemblies could be included in the NuGet packages and the .NET 3.5 support needs fixing.
Sorry if this sounds a bit negative but Common.Logging is a great tool and well worth maintaining. Thank you for your time and effort in developing and maintaining it.
Best regards, Steve Short.
The text was updated successfully, but these errors were encountered:
The http://net-commons.github.io/common-logging/ web page indicates support for .NET 2.0, 3.5, 4.0, 4.5, and more.
The Common.Logging 3.4.1 NuGet package supports .NET 3.5 and .NET 4.0 but Common.Logging.Core 3.4.1 only supports .NET 4.0.
So, no there's no support for .NET 2.0 in the NuGet packages and if I target .NET 3.5 in my project then NuGet still fails to install the version 3.4.1 packages because even though Common.Logging supports .NET 3.5 it depends on Common.Logging.Core which does not.
I can download the source code and build the .NET 2.0 assemblies but as Common.Net.snk isn't available I have to sign them using my own key. I can live with this but it's not ideal.
It would be good if the .NET 2.0 assemblies could be included in the NuGet packages and the .NET 3.5 support needs fixing.
Sorry if this sounds a bit negative but Common.Logging is a great tool and well worth maintaining. Thank you for your time and effort in developing and maintaining it.
Best regards, Steve Short.
The text was updated successfully, but these errors were encountered: