I have just finished writing an Outlook 2003 addin for automating the process of uploading pictures and creating weblog entries. Once you have the addin installed, all you have to do is email a picture as an email attachment to an email address that starts with “modblog” (and of course have Outlook pickup this email). The addin then FTP’s the image to the server, and creates a weblog entry using the Blogger API.

I started a GotDotNet workspace for ModBlogger Addin. You can go and download the addin here. Also, there is a message board for asking questions, etc. My personal modblog is at here.

As it turns out, it’s not “ModBlog” as they have it on the front of Channel9, it’s “MoBlog”, which is short for mobile blog. Anyway, I changed the name of the addin (which was a huge PIA). I need to leave the link to the GotDotNet workspace the same because I’m now linked to from Slipstick Systems (!). Can I get a w00t!

In the process of pimping ModBlogger Addin, I’m letting people know about by way of mentioning it in weblog entry comments. On the surface, someone might think that this is comment spamming. I’m not quite sure I agree (obviously, or i won’t be doing it, duh).

Since my application is free, and therefore I’m not pimping a commercial product, I don’t see how this would even be considered spam at all. Furthermore, I wrote this app for myself, and I released it to the general weblogging community so it can help them too.

I think this is sounding like I’m defending something that I’m not even accused of. So, I’ll stop.

Just so everyone doesn’t forget, Americans aren’t the only folks using the Internet (even though we did invent it). In particular, Japanese Smileys are not the same are American smileys. Check out the difference.

Thanks to Ingo Rammer for this ditty.

Ok, so I have been wrestling for the last few days with the fact that I was unable to debug .NET addins in Outlook. For whatever reason, Visual Studio would launch Outlook, and then it would crash almost immediately. I started to think that this might be a permissions issue. With that in mind, I broke out FileMon and RegMon from SysInternals.

RegMon turned up nothing, but FileMon did the trick. Just before Outlook crashed, it loaded v2.0.40301 (Whidbey) libraries, and what looked as if maybe even the Whidbey CLR. Anyhow, what I did was add an OUTLOOK.EXE.config file (yes, you can do that), with the following:

      <supportedRuntime version=”v1.1.4322″/>
      <supportedRuntime version=”v1.0.3705″/>

Well, sure as the sun rises in the East, it worked. By the way, the reason why I knew that this could be done was because I saw the runtime in FileMon look for this file, so I new the usual rules for config files applied even when the CLR is hosted in a non-managed application such as Outlook.

Oh the other thing that is the real problem is that I uninstalled the Whidbey preview, but it appears as if most, if not all, of the version 2 framework components are still there, and active none the less. I attempted to search Google for some idea on how to rid my system of verson 2, but to no avail. Anyway, as soon as XP SP2 goes RTM, I’m going to reinstall XP fresh.