Extension method for logging. A good idea?

Question

What are the pros and cons of the following extension method, in your opinion?

static class Log
{
    public static string AddToLog(this string input)
    {
        Console.WriteLine(input);
        return input;
    }

    public static string AddToLog(this string input, string format)
    {
        Console.WriteLine(format, input);
        return input;
    }
}

Usage scenario:

class Program
{
    static void Main(string[] args)
    {
        string tableName = "Bills".AddToLog("Default table name is {0}");

        "Starting...".AddToLog();
        "Creating table".AddToLog();
    }
}

Answer 1

Well, they are static to begin with, which will make testing more difficult and will be increasingly tightly coupled.

I also personally think something like

Logger.Write("Starting..");

more understandable than

"Starting...".AddToLog();

Answer 2

For me it is not very readable.

Just because you can doesn’t mean you should :)

Answer 3

, Ruby, . , , , , .

# .

, . : ? - , , , , log4net, .

Answer 4

. . , . ( , )

, , , - , , . .ToX(), MPH - , , .

Answer 5

Console.WriteLine

API ( ) , .
, log4net .Error . , .

, , .

Answer 6

, . , , .., .

, String . , , . , , .

Answer 7

The biggest problem with this approach is that it is almost impossible to embed dependencies in static / extension methods very cleanly. This means that your logging solution (assuming it should become more complex than dumping things in stdout / console / debug) must be deployed and configured for any type of testing in the project. Someday.