The Great .NET Client Divide: A Simple Example (Hopefully)
I have been getting some good feedback on writing lengthy blog articles. Right right. I try to be aware and respectful of your time. And mine, too. At the end of the day I am just some random developer that you don’t know who happens to put their thoughts on the web — and I try to keep that in mind. Additionally, I simply hate writing and hate writing long articles even more, so your guess is as good as mine as to why I put myself (and you, the patient reader) through so much agony. With that said, let’s see if I can keep this short. Please vote:
What Is It Now?
I have been checking out some awesome logging software lately, namely Serilog and a (just as awesome) complimentary logging presentation component, Seq. I have to say that Serilog is the real deal. Just look at all these sinks, JUST YOU LOOK AT THEM! That is some serious business. You can also use an amazing configuration fluent API which just might change the way I approach all my future solutions — I’ve seen fluent, but not like this. This means something, this is important!
So What Is the Problem?
Serilog is an awesome .NET logging solution. It will work in a .NET application on the server (where you can also use in conjunction with Seq), and it will work in a WPF application or even WinForms application (again, with Seq). It will work in a Console Application (with Seq), and there is even an effort to allow it to work in a .NET Core application (Seq TBD).
GET TO THE PROBLEM, DAMN YOU!!!
Ahhhhhhh… I get it.
WHEW! Please Vote