Rob Reynolds - The Fervent Coder - All Comments

re: RoundhousE – ADO.NET over SMO

Rob Reynolds — Tue, 09 Mar 2010 03:14:14 GMT

Okay - so this is working great as of revision 150. And I was wrong about all of those things I said would not work. They all work.

If you are using SMO, the batches are not split.

re: RoundhousE – ADO.NET over SMO

Rob Reynolds — Mon, 01 Mar 2010 21:29:04 GMT

Awesome! I'll take a look.

re: RoundhousE – ADO.NET over SMO

Harry M — Sun, 28 Feb 2010 18:14:39 GMT

I think SMO is redistributable www.microsoft.com/.../details.aspx

re: RoundhousE – ADO.NET over SMO

Rob Reynolds — Wed, 24 Feb 2010 22:56:04 GMT

Well - it appears the logic still isn't quite ironed out. Be on the lookout for a release sometime later this weekend!

Lessons In Building An Email Parser

Rob Reynolds - The Fervent Coder — Fri, 18 Dec 2009 09:19:06 GMT

The Classic Infinite Email Loop When building an email parser, one must think about validating an email

re: How To Check Email Programmatically - SidePOP

Rob Reynolds — Tue, 08 Dec 2009 18:47:03 GMT

This has now been updated to be used with a configurator. This looks something like this:

    private void configure_mail_watcher()
    {
           EmailWatcherConfigurator configurator = new SidePopXmlConfigurator();
           foreach (EmailWatcher emailWatcher in configurator.configure())
           {
               emailWatcher.MessagesReceived += runner_messages_received;
               emailWatcher.start();
           }
      }

I will get a post up to show it soon.

re: How To Use Windsor to Change a Deployed Application’s Behavior Without Touching a Single Line of Existing Code

Rob Reynolds — Fri, 04 Dec 2009 15:43:11 GMT

@MichaelMJ: Yes, you are correct. Technically I am still editing a configuration file and that is arguably code.

The point I am aiming for is that you could come up to an existing system and not have access to anything but the application in production and make it work differently without having to go back to the source of the existing system at all.

re: How To Use Windsor to Change a Deployed Application’s Behavior Without Touching a Single Line of Existing Code

MichaelMJ — Fri, 04 Dec 2009 15:25:41 GMT

Isn't it a bit of a misnomer to say that you aren't editing code? You've just moved your code specification to an XML file rather than having it in C#. You've done it without re-compiling the system definitely.

re: Command Line Parsing on Windows with Mono.Options

James Gregory — Thu, 26 Nov 2009 09:32:28 GMT

This is one of those things that I hand roll on every new project, and with every one think "there should be an easier way to do this!". Seems like there has been all along. Thanks for bringing this to my attention!

re: Command Line Parsing on Windows with Mono.Options

Rob Reynolds — Mon, 23 Nov 2009 20:54:31 GMT

I'm using Mono.Options on the Windows platform. You are not the first person to mention the Mono part. The Options library can be used with either Windows or Linux. Thanks for helping me see that. I will try to be more clear.

re: Command Line Parsing with Mono.Options

csharptest.net — Mon, 23 Nov 2009 18:44:28 GMT

Interesting stuff, I found myself recently wishing this was built-in to the .Net Library. Finding that it wasn't and being very tired of writing and re-writing this code I finally developed a similar approach. I'm glad to see this finally starting to eek it's way into a more core library. If your looking for a solution similar to this on the Windows platform check out: http://csharptest.net/?p=299

re: Command Line Parsing with Mono.Options

Ronald Widha — Mon, 23 Nov 2009 04:10:43 GMT

excellent stuff. I'll make an excuse to use it in a project