log4net version

[Alexandre Rocco]

I'm currently using ServiceStack on a solution that depends strictly on log4net version 1.2.10. So, my option was to move a step back and use this version on the service. Tried to configure Log4NetFactory() but it looks this has a hard dependency on version 1.2.11. Am I correct? Is there any fix to use the older version?

Thanks,

Alexandre

[Demis Bellot]

It looks like ServiceStack.Logging.Log4Net can support dependencies of Log4Net (≥ 1.2.10)

http://nuget.org/packages/ServiceStack.Logging.Log4Net 

If you do run into any issues it's pretty easy to create an adapter for a specific Log4Net version, the ServiceStack.Logging project (the src of the NuGet pkgs) has wrappers for 1.2.9 and +1.2.10 at:

https://github.com/ServiceStack/ServiceStack.Logging/tree/master/src 

Cheers,

--
- Demis

http://twitter.com/demisbellot

http://www.servicestack.net/mythz_blog

[Alexandre Rocco]

Demis,

I think that the Log4NetFactory is hard-linking the 1.2.11 version on the .csproj file:

https://github.com/ServiceStack/ServiceStack.Logging/blob/master/src/ServiceStack.Logging.Log4Net/ServiceStack.Logging.Log4Net.csproj#L65

Maybe this is the case?

Thanks,

Alexandre

On Monday, May 7, 2012 5:14:22 PM UTC-3, mythz wrote:

It looks like ServiceStack.Logging.Log4Net can support dependencies of Log4Net (≥ 1.2.10)

http://nuget.org/packages/ServiceStack.Logging.Log4Net 

If you do run into any issues it's pretty easy to create an adapter for a specific Log4Net version, the ServiceStack.Logging project (the src of the NuGet pkgs) has wrappers for 1.2.9 and +1.2.10 at:

https://github.com/ServiceStack/ServiceStack.Logging/tree/master/src 

Cheers,

[Demis Bellot]

Yeah maybe, it was linking to 1.2.10 at one stage. Its an issue cause Log4Net is (annoyingly) strong named.

IMO the best sln would be to create a copy of ServiceStack.Logging.Log4Net called ServiceStack.Logging.Log4Netv1210 with a hard reference to a 1.2.10 lib - i.e  like we do for v1.2.9.

Cheers,

[Alexandre Rocco]

Yeah demis, you're right.

I've just forked the Logging project and created a Log4Netv1210 specialized version and it works fine.

If you find it useful, I can try to submit a pull request, but I'm not too proficient in git/github processes. :)

Cheers!

Alexandre

On Tuesday, May 8, 2012 4:38:59 PM UTC-3, mythz wrote:

Yeah maybe, it was linking to 1.2.10 at one stage. Its an issue cause Log4Net is (annoyingly) strong named.

IMO the best sln would be to create a copy of ServiceStack.Logging.Log4Net called ServiceStack.Logging.Log4Netv1210 with a hard reference to a 1.2.10 lib - i.e  like we do for v1.2.9.

Cheers,

[Demis Bellot]

Sure, would love a pull-request :)

Pull requests are pretty easy, it's just a matter of forking the project, creating changes + committing to your fork then send the changes over via a pull request.

Here's a nice step-by-step tutorial that will walk you through:

http://help.github.com/send-pull-requests/

Cheers,

[Alexandre Rocco]

Demis,

Just done the pull request. 

Thanks for the info. It's quite straightforward. 

There is a change in the mindset for folks that work with VSTS like myself but that's another story. :)

Cheers,

Alexandre

On Tuesday, May 8, 2012 5:22:41 PM UTC-3, mythz wrote:

Sure, would love a pull-request :)

Pull requests are pretty easy, it's just a matter of forking the project, creating changes + committing to your fork then send the changes over via a pull request.

Here's a nice step-by-step tutorial that will walk you through:

http://help.github.com/send-pull-requests/

Cheers,

[Demis Bellot]

Sweet, just merged it in!

And welcome to Github + ServiceStack :)

https://github.com/ServiceStack/ServiceStack/commit/fdac927159362431a5efec7d3fc7f2237fe34364 

Cheers,

[Mat Arge]

Is there a particular reason, why there is no NuGet Package for ServiceStack.Logging.Log4Netv1210?