Rob Reynolds - The Fervent Coder - All Comments

re: Introducing this.Log

Rob Reynolds — Wed, 30 Jan 2013 19:25:48 GMT

@Rohan: Both log4Net and NLog support the rendering of exceptions. I take pull requests. :D

re: Introducing this.Log

Rohan Cragg — Wed, 16 Jan 2013 11:24:58 GMT

Awesome indeed!

Had you considered supporting an overload of .Error to pass in an Exception as a second parameter?

I ask because NLog supports rendering of Exception info:

nlog-project.org/.../How_to_properly_log_exceptions%3F

re: Introducing this.Log

Anonymous — Thu, 10 Jan 2013 07:15:48 GMT

" Feel free to take my work and make it better."

Meaning, go ahead and use this solution freely in any situation possible?

re: Refresh Database–Speed up Your Development Cycles

Rob Reynolds — Thu, 20 Dec 2012 05:32:28 GMT

NH version information is here: github.com/.../Roundhouserefreshdatabasefnh

re: Introducing this.Log

Rob Reynolds — Thu, 20 Dec 2012 05:29:07 GMT

And a NuGet Package - devlicio.us/.../this-log-source-nuget-package-amp-performance.aspx

re: Introducing this.Log

angol — Mon, 17 Dec 2012 20:45:07 GMT

vote for pedro, vote for nuget:)

re: Introducing this.Log

Matt — Mon, 17 Dec 2012 20:23:05 GMT

It would be great to have a nuget package

re: Introducing this.Log

Matt Davey — Mon, 17 Dec 2012 16:23:39 GMT

@Mark Rendle I had the same thought but unfortunately you can't get the name of the type with caller info attributes, just the method/file/line.

re: Introducing this.Log

Stuart — Mon, 17 Dec 2012 14:09:24 GMT

In fact, going off my earlier comment, I think you could replace your public static class Log with:

public static class LogManager

{

static readonly ILog NullLogInstance = new NullLogger();

public static Func<Type, ILog> GetLog = type => NullLogInstance;

}

(From Caliburn.Micro), then in your extension method class you use LogManager.GetLog(typeof (T));

re: Introducing this.Log

Mark Rendle — Mon, 17 Dec 2012 10:00:27 GMT

In C# 5, adding the [CallerMemberName] etc attributes to the extension methods could improve this still further.

re: Introducing this.Log

Stuart — Mon, 17 Dec 2012 08:38:01 GMT

This looks pretty good. Some combination of this and the way that Caliburn.Micro manages logging (see caliburnmicro.codeplex.com/.../1c05274733b7) would be pretty awesome.

re: Refresh Database–Speed up Your Development Cycles

Raif Harik — Sun, 16 Dec 2012 19:23:14 GMT

Hi, I'm interested in the NH version. I see the nuget but don't see any info on the source or how to use it. Somewhere you mention using FNH diff scripts that are generated but I don't know anything about that either. Can you expand on this subject?

Thanks,

Raif

re: Introducing this.Log

Sun, 16 Dec 2012 04:15:23 GMT

Sticking Lazy around the concurrent dictionary seems unnecessary (construction of the dictionary takes very little time tested with 100000 iterations and a stopwatch).

Conversely, the Log class could be cleaner if you used Lazy(T)

Have you considered InitializeWith(Func(T) teaFactory)* instead of storing the type and using Activator.CreateInstance()?

* parentheses instead of angle brackets, because I'm not sure what gets swallowed.

re: Introducing this.Log

Jega — Sat, 15 Dec 2012 19:10:31 GMT

Hi Rob

This is so cool. Great if you could create a Nuget package.

Thanks

Jega

re: Introducing this.Log

Jega — Sat, 15 Dec 2012 19:09:00 GMT

Hi Rob,

This is cool. It would be great if you could create a Nuget package for it.

-Jega