Greg Beech's Website

June 2007 - Greg Beech's Tech Blog

Sort By: Most Recent | Most Viewed | Most Commented

  • Pragmatic exception management, Part 2

    In the first entry in this series I looked at what medium-to-large companies and developers want from an exception management framework, and derived some requirements from this. To recap, these are the high level requirements, which you'll note that no current framework is even close to meeting. Publish all exceptions to the Event Log No configuration files required Auto-generate boiler plate exception...
    Filed under: ,

  • Quick and dirty projects are rarely quick but always messy

    We've all been on them before. A salesman gets a request from a client to implement a "simple process", and the client books ten days work at a fixed cost which means you're obliged to deliver in that time. You go in, do the work to the minimum standard as that's all the ten days allows you to do on a project that should really have been twenty-plus days, and then leave. And that's...
    Filed under:

  • Pragmatic exception management, Part 1

    At Netstore we've spent quite some time over the last six months implementing a custom diagnostics and exception management framework. You might think this is a sign of the Not Invented Here syndrome, which I guess it is, but believe me we wouldn't have spent the equivalent of a fortune in consulting days building it unless we thought there was a good reason. The trouble is, after evaluating...
    Filed under: ,

  • Partial message encryption in BizTalk pipelines

    If you are receiving messages which contain potentially sensitive data, for example credit card details or bank identifier codes, then you may not want to allow these to enter BizTalk unencrypted as there will be plain-text copies of the data in the message box database. On the other hand, you don't want to encrypt the entire message as its type and at least some of the content are probably needed...
    Filed under: ,

  • Why do we have different types of exception?

    The short answer is to allow them to be handled differently in a programmatic manner. You've probably done it hundreds if not thousands of times - creating a try/catch block and catching an exception based on its type to handle it in a particular way. So the headline question in itself isn't particularly interesting; however the answer's simple premise leads us to a couple of the fundamentals...
Copyright (C) Greg Beech. All rights reserved.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems