Thank you for submitting this cool story - Trackback from DotNetShoutout…

There is no helpers class - my implementation is basically the same snippet as above, with the difference that it handles exceptions (and creates faults) that are specific to my application.

However, I find myself applying this pattern in more and more situations (not only WCF, but everywhere I just want to make sure proper exception handling is made). For example in order to log an exception before rethrowing it again:

//deviation of the pattern that logs every
//exception before rethrowing it (simplified)
public static T SecureFunc<T>(Func<T> func)
{
  try
  {
    return func();
  }
  catch (Exception e)
  {
    LoggerService.GetLogger().Error(e);
    throw;
  }
}

will you be making your FaultException helpers available for download?

You can easily declare the control in code:

TaskbarIcon tbi = new TaskbarIcon();
tbi.Icon = Resources.Error;
tbi.ToolTipText = "hello world";

Nonetheless, thanks for making the plugin (and for managing to decipher my comment despite my inability to remember the tag for code snippets)

One question, though, when I insert a class, it essentially inserts a “” tag for the class. Is there a way to have it simply insert the class into the style that is already present?

For example if I were inserting the class “bar”:
content here
currently becomes:
content here
is it possible to have it become:
content here

Just curious.

Either way, thanks for developing this plugin — a super help for me.

public static string GetRandomString(int length)
{
if (0 >= length) throw new ArgumentOutOfRangeException();

const byte lower = 0×21;
const byte upper = 0×7e;

int resultIndex = 0;
char[] result = new char[length];
byte[] buffer = new byte[length];
var rnd = RandomNumberGenerator.Create();

while (resultIndex < length)
{
rnd.GetNonZeroBytes(buffer);
char[] temp = buffer.Where(b => lower &lt= b && b <= upper).Select(b => (char)b).ToArray();
if (0 != temp.Length)
{
int l = Math.Min(temp.Length, length - resultIndex);
Array.Copy(temp, 0, result, resultIndex, l);
resultIndex += l;
}
}

return new String(result);
}

public static string GetRandomString(int length)
{
if (0 >= length) throw new ArgumentOutOfRangeException();

const byte lower = 0×21;
const byte upper = 0×7e;

int resultIndex = 0;
char[] result = new char[length];
byte[] buffer = new byte[length];
var rnd = RandomNumberGenerator.Create();

while (resultIndex lower <= b && b (char)b).ToArray();
if (0 != temp.Length)
{
int l = Math.Min(temp.Length, length - resultIndex);
Array.Copy(temp, 0, result, resultIndex, l);
resultIndex += l;
}
}

return new String(result);
}

But I found the answer. All you have to do is visit TinyURL’s preview page (http://tinyurl.com/preview.php) and click “enable previews.” The service will add a cookie to your browser so that every time you click on a TinyURL link you’ll first be taken to a page showing the complete URL. Now I can see that your TinyURL resolves to this URL: http://blogs.infragistics.com/blogs/andrew_flick/archive/2009/05/13/netdrives-free-utility-to-map-network-shares-drives.aspx.

Now I can click TinyURLs without having to worry about seeing pictures of trannies or CP at work. Yay!

However, I’ll keep the naming proposition in mind. Although L4G doesn’t sound as slick as SLF. This *is* a show stopper.

public class MyScheduler : Scheduler
{
  public IEnumerable<Job> GetJobs()
  {
    lock(SyncRoot)
    {
      return Jobs.Select(jc => jc.ManagedJob).ToArray();
    }
  }
}

Quartz looked like an obvious choice from the specs, but it turned out to be too heavyweight for me. It has maintained compatibility back to .NET 1.1, and also comes with a dependency to Common.Logging that was a bit of a show stopper to me. And Silverlight compatibility is of course out of the question as well.

However, this doesn’t mean that my library is necessarily the better solution for your project: I guess my approach and Quartz just satisfy different requirements: Quartz is quite a beast and brings a lot to the table in one package (including database storage). Mine is a leightweight solution that can be *very* easily integrated and adjusted if needed, and leverages new language features in order to provide a lean API.

HTH,
Philipp

Edit: Exception handling implemented and published with version 1.0.2. Thanks for the feedback, Peter

I’d rather see the responsibility to handle failed jobs within the client code (on the callback method). However, I’m thinking about adding a callback handler for exceptions into the Scheduler class - mainly in order to handle potential issues with a failing ThreadPool (OutOfMemoryException), but I might extend the mechanism in order to report job exceptions as well. Hmm, need to think about this first…