Technical people respond to questions in three ways:

1. It is technically impossible (meaning: I don't feel like doing it);
2. It depends (meaning: abandon all hope of a useful answer);
3. The data bits are flexed through a collectimizer which strips the flow-gate arrays into virtual message elements (meaning: I don't know).

"Insanity: doing the same thing over and over again and expecting different results."
-- Albert Einstein

So, our friends over at xkcd supply the content of the day

Well, BlogEngine.NET 2.0 has finally been released.  Here is the official release.  One of the most notable updates in this release is that BlogEngine.NET has made the leap from .NET 2.0 to .NET 3.5.  For a list of new features in BlogEngine.NET 2.0, visit here.

So, as soon as I get off my butt, I will upgrade my current version from 1.6.1.0 to the new 2.0.0.44 release.

There are a few good articles over on RTUR.net that you may want to look into:

• Some thoughts on SPAM
• Hosting BlogEngine.NET 2.0 on GoDaddy

As I delve into the upgrade, I'll take some notes and screen shots and let you know how I overcome any issues.

Most sites contain a web server file called robots.txt, which is used to instruct spiders to ignore certain directories on the site.

If you’ve never heard of robots.txt files before, they’re simply a  text file placed on a web server containing a set of rules to control how web spiders crawl a site.  These files were developed in 1994 by Martijn Koster.  Even those these robots.txt files can now be found on most websites, they are rarely viewed by humans.

These little files have been known to hold small easter eggs from time to time.  This brief article points out a few of the most well known hijinks and shenanigans of the robots.txt file.

Last.fm

Unlike other websites, Last.fm’s robots.txt file includes additional instructions in the form of Isaac Asimov’s famous three laws of robotics:

1. A robot may not injure a human being or, through inaction, allow a human being to come to harm.
2. A robot must obey orders given it by human beings except where such orders would conflict with the First Law.
3. A robot must protect its own existence as long as such protection does not conflict with the First or Second Law.

User-Agent: *
Disallow: /music?
Disallow: /widgets/radio?
Disallow: /show_ads.php

Disallow: /affiliate/
Disallow: /affiliate_redirect.php
Disallow: /affiliate_sendto.php
Disallow: /affiliatelink.php
Disallow: /campaignlink.php
Disallow: /delivery.php

Disallow: /music/+noredirect/

Disallow: /harming/humans
Disallow: /ignoring/human/orders
Disallow: /harm/to/self

Allow: /

Google

In October 2008, Google slipped a hidden message into the rules of their robots.txt file for Halloween:

User-agent : zombies

Disallow : /brains

The change was covered by Google’s Web Spam expert Matt Cutts in his personal blog. 

Reddit.com

Finally,we come to the robots.txt file for the site www.reddit.com.    Hidden in the text are instructions to two popular robots, Futurama’s own Bender, and Gort from the 1951 film, The Day the Earth Stood Still.


# 80legs
User-Agent: 008
Disallow: /

# MSNBot
User-Agent: msnbot
Crawl-Delay: 20

User-Agent: bender
Disallow: /my_shiny_metal_ass

User-Agent: Gort
Dissalow: /earth

So, how much fun have you had with these files?

SharePoint 2007 can only be installed on the Windows Server family platform. As a developer, I need to be able to develop on this platform.  However, my development platform is currently either XP/Vista/7 based running VS 2008.  What doesn’t make any sense to me is that all the tools require WSS to be installed locally, on a 2003/2008 Server platform.

The recommendation for MOSS development was always to get a VM to run W2k3 with MOSS and Visual Studio.  Ok, so what do you do if you do not have the time to build such a platform, or what if you do not have access to a server OS.

If you try to install the Visual Studio 2008 Extensions for Windows SharePoint Services 3.0 Tools (VSeWSS) on a workstation you’d probably fail and get the following error: “This product can only be installed if Windows SharePoint Services 3.0 has been installed first”. So the only thing we can do is either conform to the VM path, or we can hack the installer into thinking MOSS is installed.  We are going to hack!

You might as well make sure to download the latest extensions installer. I installed the Visual Studio 2008 extensions for Windows SharePoint Services 3.0, v1.3 - Feb 2009 CTP on my work machine.

Before continuing into opening the Regedit tool, be aware that messing around with the Windows registry is not supported, and not recommended by Microsoft.  However, being a computer nerd, I don't give a poop.  I can always fix it

Now open the regedit.  My work environment is running Windows 7, so I have to make sure to open regedit and run as an administrator.

Make a quick backup of the registry, just in case. If you do not know how to do this,  Do not pass GO, do not collect $100.  Honestly, if you cannot make a registry backup or do not feel comfortable hacking the registry, you probably should not continue.  That was my only warning.

Create the following keys and the string value:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0]

"Sharepoint"="Installed"

Tada!  Now when we run the installer, the installer has been tricked into believing that we have Sharepoint Services installed locally. 

I also recommend adding the SharePoint and MOSS assemblies into the GAC. The assemblies can be found in any SharePoint server under the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI folder.

Here is an interesting, but true, article on how NOT TO BE the asshole architect at your organization.  Too often more than not, architects do a piss poor job at following the 7 principles this author has pointed out.  I have been known to architect solutions in that role and always try to act accordingly and take the developer's perspective into mind. I personally recall one or two instances where an architect broke several of these rules when dealing with my development team. Believe it or not, it took several years for those wounds to heal enough for my team to feel comfortable working with this individual.

Check out this article, it is quite good. CLICK HERE FOR THE ASSHOLE ARCHITECT ARTICLE

Well, as you probably know, I utilize BlogEngine.Net, for my mediocre blogging needs.  My needs are somewhat mediocre, but I feel that this tool can sufficiently provide the functionality that some business owners may desire.  Of course, there is always some customization.

Four days ago, I upgraded the blog to the latest stable release.  I was pleased to see that the latest stable release 1.6.1.0 has some included features for ReCaptcha and AkismetFilter, along with a better interface for managing comments.  As a software engineer, I found the upgrade process simple, however, somewhat dissapointing due to a couple of small bugs I encountered.  Not a biggie though.

!!!Results so far!!!

So far, the combination of filters I am utilizing are stopping 100% of the SPAM.

Filters:

• StopForumSpam - a filter that is built into the blog engine and does not allow any configuration
• ReCaptcha - that annoying little thing that makes you put in words that are a bit fuzzy and hard to read
• AskimetFilter - this filter is the same one used on countless numbers of WordPress blogs.

I have my moderation settings set to automatically moderate comments based on the filters.

Now, I will be the first to admit that I do not have a lot of people leaving comments on my posts.  I get roughly four to five thousand hits a month on this blog, most of those are probably from me.  However, I was averaging around 10 spam comments per day.  So far, so good.  I can honestly say that the settings and filters I am using are currently catching 100% of the SPAM attempts, and that no SPAM comments have been posted live.

Well, I will keep an eye on it and report my findings later in the month.

Hope this helps someone.