My hosting provider is having email issues right now.  Any email sent since last night to nick-at-nickschweitzer-dot-net has not gotten to me, and may be lost.  I still don't appear to be getting any email sent to that address.  If you're trying to get a hold of me, try sending to schweitn-at-gmail-dot-com.  I'll update this post as the situation changes.

Update:  Email is being delivered to my normal email addresses again, but I'm afraid anything sent last night until mid morning today was more than likely lost.  If you emailed me something during that time frame, please send it again.

Well folks... I'm off to the west coast for a little while.  Blogging will be intermittent at best.  Stay well, and leave the light on for me.

So along with the recent news that I've joined Facebook, you can also follow me on Twitter.  One of the things that I kept hearing at Deeper in .NET a couple weeks ago was, "So what's your Twitter name?" and "Aren't you on Twitter yet?".  I heard it from so many people, that I finally decided to give it a try.  And if you're on Twitter and I should know about, feel free to drop your Twitter name in the comment thread so I can add you too.  Some of my blogs also feature my latest Twitter updates in the sidebar.

For anyone trying to get a hold of me, it seems as if my two domain email addresses are not forwarding properly at the moment.  So if you've been emailing me at nick-at-nickschweitzer-dot-net or nick-at-thecodingmonkey-dot-net and I haven't responded, please try me at schweitn-at-gmail-dot-com.  I have a support ticket into my hosting service, so hopefully it will be resolved soon.

Update:  Everything got resolved some time last night, and I even got an influx of emails from throughout the day.  Nice to not lose anything, even if they were delayed several hours.  I actually do prefer nick-at-nickschweitzer-dot-net however, since at some point, I may stop using gmail, and if everyone sends to that address, I don't have to worry about losing too much email in the switch.

This obviously doesn't affect me, but does potentially affect many of the other blogs I read:

Security analyst David Kierznowski shocked bloggers yesterday with a survey showing that 49 out of the 50 WordPress blogs he checked seem to be running exploitable versions of the widely used software. He said, 'The main concern here is the lack of security awareness amongst bloggers with a non-technical background, and even those with a technical background.' Mr Kierznowski also uncovered recent vulnerabilities in WordPress plugins that ship by default with the software, adding: 'WordPress users developing plugins must be aware of the security functions that WordPress supports, and ensure that these functions are used in their code.'

So if you run WordPress on your own domain, check your version and upgrade if you are running anything less than 2.0.10 or 2.2.

Just a quick note.  I've disabled trackbacks for a while since I've been getting more trackback spam than actual trackbacks.  I've got a couple changes to make to the code base I use, and will re-enable them when those have been completed.

Just wanted to give you all a heads up that I'm going to start using FeedBurner to supply my RSS feeds.  Fortunately, dasBlog is so cool, that if you give it the location of your FeedBurner feed, it will automatically redirect people who use your existing feed to the new one.  So hopefully, you'll never know it happened.  But if for some strange reason you stop receiving my feed, you'll need to come back to my homepage and get the new feed address.

As you know, Blogging isn't free for me anymore, and I don't get enough traffic to support real advertising yet.  But, I'd still like to make this little enterprise of mine self sufficient.  As you may know, Phel at The Confidentials has started up a new Cafe Press store (which you should definitely check out).  What you might not know is that I've been working on a similar enterprise, and have just opened one up myself called CubicleRevenge.  You can find it at CubicleRevenge.com.  Right now there are three designs with several more on the way in the next few days.

So head on over and check them out.  And if you feel so inclined, support my blogging with some nice merchandise.  And as Bartles and James would say... Thank you for your support.

As I mentioned last week, and as some of you continued to notice, my blogs were having some issues after I moved to my new domain.  As I've mentioned before, I chose a great tool for blogging called dasBlog.  It is used by hundreds of people, has an active developer community, and is used by many high traffic blogs.  I felt like I made a solid choice, and still do.  Unfortunately, I took the word of one of the community members about which hosting service to use.  Big mistake.  The hosting service I was using up until yesterday was BoundGrid.net.  They offered a pretty good package, and a very reasonable price.  But as the old saying goes, you get what you pay for.  And what I didn't get was good service.

I'm sure that if everything went smoothly, I would have loved them like the person who had originally recommended them.  But the true test of any company is how they react when you are having problems with their service.  Last week, The World According to Nick was crashing about 3 to 4 times per day due to Out of Memory Exceptions.  This also had the effect of taking down The Coding Monkey.  The sites would automatically recycle, but would be down for 5 to 10 minutes while this happened.

When I originally emailed the technical support group, they looked at the site, said it was up (it had recycled by then), and told me to contact them when it happened so they could "investigate further".  I sent them my copy of the error logs that showed exactly what was happening, but they insisted they could only do something if the site was down.  For a problem that occurs randomly, this is not an easy thing to do.  Luckily for me, I was able to catch it when it was down, and I immediately contacted them.  Their "solution" was to perform an iisreset and thank me for using their service.

This would happen 3 to 4 times a day, and each time I happened to notice it and saw the site was down, I would contact their technical support group, and all they would do was perform an iisreset.  As I continued to escalate my complaint, their response turned into "check your code".  Of course, I'm running production level code that hundreds, if not thousands, of other people are using, but I did anyway.  I also contacted one of the lead developers for dasBlog (Scott Hanselman), and asked for his help.  He was baffled and had never heard of anything like this.  We started asking basic questions about the environment I was running on, to try to see how the site was configured.  BoundGrid basically told me that I had more memory than a site like mine needed, and refused to answer my very specific questions about where I was running.

At this point, not only had I looked at the dasBlog code, but I had made more than a half dozen configuration changes to dasBlog that might ease the memory requirements.  None of these changes worked.  On Monday I finally got sick and tired of it all, and decided to switch hosting providers.  I chose StormHosts, and I couldn't be happier with my decision.  They're slightly more expensive, but their service and support has been fantastic thus far.  When I originally copied my site up to their servers, there were some permissions issues that were not allowing me to post.  They worked the problem through, kept in constant contact with me, and gave very personal responses that showed that they knew what they were looking at.  They also host several other major bloggers who all use dasBlog.  I highly recommend them.  As for BoundGrid, I can only assume that their technical support team's only previous experience with computers was working the automated fry machine at McDonald's, and being handed a copy of "So You Want To Be a Network Administrator".

Thankfully BoundGrid offers a 30 day money back guarantee, which I am taking full advantage of, so my mistake won't cost me any money.  However, it has cost me great frustration, time, and effort.

Must Be Extendable: This was probably my biggest frustration with Blogger. Although you could do a lot with the templates if you worked at, it lacked certain basic features, and they seemed in no hurry to add any. This meant that I was constantly trying to pull features in from other services to complete my blog package. It made things much more difficult than it needed to be. Although many people prefer WordPress for switching from Blogger, because it's written in PHP (which I only have a cursory knowledge of), customization would be harder for me. Because dasBlog is written in C#, which I know like the back of my hand, customization for me is extremely trivial. In fact, I've already written several macros which are being used on my blogs, which took about a total of 1 hour to write and test.

Had to Run Locally: I wanted to be able to run a version of my blog locally on my laptop. This would allow me to do all the importing and testing locally on my machine, before I even bought server space. That way I could get everything exactly as I wanted it before I moved to my server. This goes hand in hand with picking a .NET blog engine, because I already have all the tools available on my laptop without any extra configuration. WordPress requires PHP and MySQL to run... neither of which I have. dasBlog only requires ASP.NET with no database requirements since it uses XML files as its datastore. This has an added advantage of making it cheaper to host, since most hosting services charge extra if you want to run an instance of a database on your domain.

Import Old Content: I had to be able to import all my old content. That means posts, comments and trackbacks. Though getting this data out of Blogger was going to be a pain no matter what, I wanted to make sure that importing wouldn't also be difficult. dasBlog has an extremely well thought out Data Access Layer that made this process trivial. I can't stress enough how simple it really was to get my data into dasBlog.

Preserve Permlinks: They're permlinks, not templinks. I get a lot of hits via Google, am on many people's blogrolls, and have a lot of old posts which people have linked to while I've been blogging. One of my biggest blogging pet peeves is when you follow a permlink, and you find out that the blog has moved, but you simply get forwarded to the person's homepage. I wanted to make sure that I could change my Blogger template in such a way that people going to a specific post of mine would get forwarded to that same post on my new blog. Once again, dasBlog made this simple because you can pick the unique identifier for imported posts.

Active Developer Community: I wanted to make sure that whatever engine I chose was still being actively developed, and that there was an opportunity for me to get involved. I haven't really been heavily involved in any extra development since I was participating in Winamp3, and wanted to get involved in something again. dasBlog is still being actively developed on SourceForge, and there is an opportunity for me to get involved.

Extra Blogging Features: Of course, one of the primary reasons for moving off of Blogger was that it didn't offer certain basic features. I wanted Categories, built in Trackbacks, and built in file uploading. dasBlog does a very good job with all those things. In addition to that, it has built in ability to cross-post between multiple sites (which is great since I was doing that manually from time to time between my two blogs), and has a really sweet search engine that outputs search results using your template with word highlighting.

Don't worry, my next post will include all the steps and code that I wrote to do everything I've described here so that if you want, you too can move from Blogger to dasBlog.

Welcome to the new home for The Coding Monkey.  I've moved both of my blogs to their own domains.  You can find The World According to Nick at this new location.  My blogs are being powered by a very cool .NET blogging engine called dasBlog with lots of great features.  Importing my old posts along with the comments was very easy.  In the next few days, I'll post a more complete informational post on how to import your Blogger posts and comments into dasBlog, along with all the code you'll need right here.  I've also written some macros for dasBlog (which allows you to extend its functionality) which I'll also provide here.

In the mean time, take a look around (the Search feature is really sweet) and stay a while.