tag:blogger.com,1999:blog-15495643725616387662010-09-04T16:27:40.810-05:00Technology, etc.The Object Guynoreply@blogger.comBlogger12125tag:blogger.com,1999:blog-1549564372561638766.post-20856653748695604822010-09-03T16:50:00.002-05:002010-09-04T16:27:40.826-05:00

Twitter now requires OAuth in order to use their API. I thought it might be nice to provide a new Logger that tweets using Twitter's OAuth. Unfortunately, compared to the original TwitterLogger, the code has ballooned quite a bit. However, if you want to use one of the available Twitter API libraries, then most of the code here would go away and you'd be back to a tiny Logger subclass that

The Object Guynoreply@blogger.com0tag:blogger.com,1999:blog-1549564372561638766.post-13006227077350324482010-03-24T14:43:00.010-05:002010-03-24T14:58:57.296-05:00

If you haven't heard of Logverse, it's a service that allows applications to log to it. And just about anything can be logged to it--errors, user actions, debug information... whatever you want. It's perfect for applications out in the field, like desktop and mobile applications. But even web or other server applications can take advantage of it. You don't need to use a logging framework to use

The Object Guynoreply@blogger.com2tag:blogger.com,1999:blog-1549564372561638766.post-69026334495954911112010-03-19T01:05:00.000-05:002010-03-19T01:05:20.449-05:00

The Object Guynoreply@blogger.com0tag:blogger.com,1999:blog-1549564372561638766.post-85169839265046771702010-03-14T12:21:00.002-05:002010-03-14T12:21:57.408-05:00

Logverse is coming...

The Object Guynoreply@blogger.com0tag:blogger.com,1999:blog-1549564372561638766.post-37831169082234700702010-01-02T11:00:00.000-06:002010-01-02T11:00:54.218-06:00

Obviously something is wrong when a logging framework is so complicated that people feel they need a special GUI to configure it. This is what I'm talking about. My framework doesn't require any configuration. But it supports it, if that's your style. It's intuitive enough--just like the rest of the framework--that you won't feel the need to call The Geek Squad to help you figure it out. Watch

The Object Guynoreply@blogger.com0tag:blogger.com,1999:blog-1549564372561638766.post-38785260567179065112010-01-01T17:23:00.000-06:002010-01-01T17:23:53.758-06:00

In light of my previous post, I thought it would be a good idea for me to demonstrate logging in a multi-threaded application using my framework. Watch this very short video. It's just a little over 3 minutes long.

The Object Guynoreply@blogger.com0tag:blogger.com,1999:blog-1549564372561638766.post-75159068120146120082009-12-31T14:33:00.002-06:002009-12-31T14:46:56.887-06:00

I don't really want to bag on another logging framework, but I've come across many posts that are downright scary. Here's an example of a situation with one of the most popular logging frameworks. Read down a bit and you'll hear about deadlocks that happened every day--until they removed that logging framework. I've also read about other serious deadlock issues with that framework. But posting

The Object Guynoreply@blogger.com0tag:blogger.com,1999:blog-1549564372561638766.post-40513553285853454542009-12-31T13:19:00.005-06:002010-01-09T12:17:27.735-06:00

Yes, the pun was intended. Many ASP.NET developers think that having code in the Application_Error method in Global.asax.cs is adequate for dealing with any unhandled exceptions within their web application. While it usually is adequate--for most basic web applications, there are particular cases where this simply won't catch all errors. Specifically, if you have code running on the server that

The Object Guynoreply@blogger.com2tag:blogger.com,1999:blog-1549564372561638766.post-46971658003619544452009-12-29T11:35:00.001-06:002009-12-29T11:39:00.188-06:00

An interesting question in a tweet caught my eye, and I thought I would attempt to provide an answer. To paraphrase, why are there so many logging frameworks for .NET, especially when there are perfectly capable facilities built-in? Ill start off by saying that I think there are probably more logging frameworks than are necessary, simply because some have come along more recently which add very

The Object Guynoreply@blogger.com0tag:blogger.com,1999:blog-1549564372561638766.post-88101921809303983182009-12-27T11:34:00.003-06:002009-12-27T12:40:24.366-06:00

There are far too many managers who think every software developer is a round peg--a "resource"--who can simply be replaced by another. Ever been served by a worker at a Mexican fast food restaurant who didn't know how to roll a burrito? How about a sandwich shop where the person behind the counter couldn't slice the foot-long sub without tearing it up? Okay, it isn't the best analogy. And

The Object Guynoreply@blogger.com1tag:blogger.com,1999:blog-1549564372561638766.post-6897763800179333562009-12-25T11:32:00.005-06:002010-09-03T16:52:52.126-05:00

[UPDATE! Look here for the OAuth version.] Yes, using The Object Guy's Logging Framework it is incredibly easy to create a logger that will write to Twitter. Here's a sample: public class TwitterLogger : Logger { protected override bool DoLog(LogEntry aLogEntry) { // without this, you may receive a '417 Expectation Failed' error ServicePointManager.Expect100Continue = false;

The Object Guynoreply@blogger.com5tag:blogger.com,1999:blog-1549564372561638766.post-6361274110150184502009-12-24T18:48:00.016-06:002010-01-23T21:44:19.598-06:00

Sloppy code, unfortunately, is ubiquitous. Sometimes it's due to laziness; other times to ignorance, as in: "it never even occurred to me to do it otherwise." I'd put the example I use in this post as one of the latter for most people. So you want to store something in Session? Easy. Session["MyString"] = "this is a string I'm storing in session." Then, somewhere else in your application you

The Object Guynoreply@blogger.com1