Archive for category blog
I’ve finally caved in and created a Twitter-account today, you can follow me at http://twitter.com/haugern!
I have been "stuck" in Visual Studio 2005 for a while, but when we now jumped to Visual Studio 2008 recently, I missed a tool I’ve been using to blog my code. As the heading states, this is Copy Source As HTML. They have not released an updated version, but Guy Burstein comes to the rescue with an updated addin.
Reading the comments it can seem to be some different "opinions" about where to put it, but I just made an Addin directory under Visual Studio 2008 in My Documents in Windows XP and extracted it there.
//And it works like a charm!
And good luck with that. 2007 was a great year overall, and I’m hoping 2008 will be just as great.
I’m starting the year adding my blog to the Technorati community. Do place my site in your favourites if you like what you read.
I also have a new year resolution regarding this blog; there will be a post at least once a week.
Phuh… then I’m saved the first week
I have a writers block. After a couple of blog posts I have a writers block. Isn’t it just sad.
Well, it’s just partially true. I’m not out of ideas or drafts, I have several 90% there. But I’m reluctant to finish and publish them, I’ve come down with what I think is a serious lapse of self confidence.
The last months I’ve been reading up on a lot of .NET related issues. I have found great blogs, written by people I think is the front figures in today’s .NET world (you can see them in my blog roll). These have inspired me to share what I know and to start my own blog, but now I’m being discouraged by the same people because I can’t write like them (yet)!
For a blog to be interesting, the person writing it must know what to write about or how to write about it. If the person knows their way around both issues, you have a blog superstar.
Jeff “Coding Horror” Atwood is one of those superstars, and he recently wrote a blog post about how you shouldn’t be a commodity blogger. I’m certainly not an expert in any field, nor am I a wizard with words, so where do I start?
Atwood says it in the end, it takes an effort. Another superstar and a personal favorite of mine is Joel Spolsky, and from this article I quote:
Writing is a muscle. The more you write, the more you’ll be able to write.
Because if I want to get better, I have to practice. Practice makes perfect is an old proverb that certainly fits the bill. And to practice I have to write this blog, even though it still is a commodity.
The main problem is to live up to expectations, my expectations.
I’m putting myself out there, no filter applied, and I’ll try to speak my mind. I’ll have to face my fears.
And for the rest of you trying to blog about something, Chris Garrett gives us a pat on the back with this post.
Phew… It helped writing this. Maybe one of the other below average posts will reach the public as well after this.
To get this blog up and running I finally took the step of ordering a web hotel. I have long planned to host it myself, but I can’t seem to find the time to assemble the machinery, nor do I find the machinery (in my basement) suitable for the task at hand.
The history so far…
So, last week (Wednesday June 27th) I was browsing the web to find a proper host. I originally wanted a windows host, so I could make my pages in ASP.NET as this is my natural habitat. I had also been looking at some blog-applications for ASP.NET, like Subtext, but it seemed to require a SQL database for storage. And you’re not going to get SQL hosting for free.
The simple solution had to prevail. My one requirement was really that it could host this blog, my technical preferences set aside. Maybe a good chance to brush up my PHP skills, or possibly take a look at Ruby (on Rails)?
OK, so lets get back to the headline. I found a host, www.one.com, which was cheap and seemed to have what I needed. I ordered the smallest solution, got the receipt and I thought I was on my merry way to blogging-land in no time, no time at all….
The steps to change my registrar (for later reference)
The first thing I had to do was getting the authorization code from my current registrar. As of October 29, 2006, you have to get this for all .COM and .NET domains from your current registrar.
So I log in to my current registrar, navigate my way through to a link called “Get Authorization Code” and click once. Ouch. I can’t do that. Or at least that’s what I’m told, and it is rather cryptic as to why I’m not able to do so.
Scratching my head some, and reading the FAQ tells me that I can try to UNLOCK my domain (did I ever LOCK it?). So I unlock the domain and voila; the “Get Authorization Code” link works. I take the code and enter it into the new registrars system.
After a couple of hours I receive two (seemingly) identical emails from my new registrar telling me to confirm I want to transfer the domain. Looking like it’s a mistake sending me two (still seemingly) identical emails I just reply to the first through a link in the email, confirming I want the transfer to continue. It gets rather late that first evening so I go to bed confident I’ll be able to blog some the next day.
The next day I’m trying, waiting, and trying again to see if the domain has transferred, but it does not seem to have been updated. There’s no indication or status on either registrars, so I turn to the online help at my new registrar.
He asks me if I have confirmed the email from the day before, and even if I had, he couldn’t see the status. As I was leaving, I told him about the mistake with the identical emails. “That’s not a mistake” he proclaims, “if you are listed as both Registered Name Holder and Administrative Contact, you will have to confirm both emails!”
So please make a bigger difference in the emails than just the link to confirm! A simple line saying which role the email was to, or how about telling me so in the topic!
And then I waited for the transfer to really go through (in my imagination anyway), because nothing happened. Ever. Until Sunday, three days after I confirmed the transfer. And what do you know, it’s a INVERSE CONFIRM email from my current registrar. Yet another security instance!
The polite email from my current registrar provides med with a link if want to cancel the transfer. And if I don’t, it will automatically be transferred in 72 hours…. read my lips: 72 HOURS. Hey, where’s the transfer now link?
Well, at least I knew what I was waiting for this time around.
The happy ending
Well, you’re reading my blog now, so the transfer must have gone through one of these days. It took exactly one week from I ordered the transfer until it actually got through.
On a positive note I should mention that I do appreciate that the security surrounding the domain transfer is thought of, but there’s always the classic trade-off between a great user experience vs great security.
Below is a sequence diagram detailing what was going on and in what order. I’ll remember to take a look at it the next time I’m transferring a domain!