Hi, everyone. The Microsoft Developer Tools and Services folks have been kind enough to give my blog a new home. The new site has a mobile-friendly design, and redirections have been put into place¹ so that links to the old site will come here.²
The Developer Tools and Services folks also created a really nice graphic for me, which I’ve put at the top of the home page, though you don’t get the full effect unless you’re on a large screen. Sorry.
I’m still trying to figure out the new site, so don’t be surprised if there are things that look weird. In particular the formatting of most posts is messed up. I’m working to fix them in my copious spare time, but it will take a while to update over 5000 articles. I’m working backwards, so the oldest posts will be the last to be updated.
The new site doesn’t give me as many customization opportunities as the old site did, so my SVG and CSS magic diagrams may not come out right. I’ll work with the blog hosting folks to see how much of it I can get working again, but my first goal is to fix the worst of the formatting issues.
One thing you’ll probably notice is that comments from the old site were not carried forward. Sorry.
If you have other questions about the blog migration, you can check the Developer Blogs FAQ to see if they’re answered there.
If you have questions about the new blog site that are not answered in the FAQ, you can ask them here and I’ll try to find answers to them.
¹ Redirections for posts from February and March of this year haven’t yet been set up. Thanks for your patience.
² This blog has moved so many times, you can probably get some sort of frequent-traveler reward for going to a really old link and redirecting through multiple sites before finally landing here.
It should not have taken me four minutes to figure out how to post here again.
Now I am tasked with revising our Visual Studio toolbar yet again. I only did that last year. Because Microsoft no longer has stable APIs. They want to blame developers for their own ineptitute. "Asychonous loading?" The VS team thinks that will solve their problem? VS is dog slow. "Asyncrhonous loading" will not solve their problem. VS 4.x will fire up much faster on far weaker hardware. So now, because of Microsoft's mistakes, I have to do something twice? Three times? Four times? I've...
And BTW Ramond — and I know this might be heresy… I personally have always belived that Windows has a better design that of Unix/Linux. Partially, because I dont want some stupid clone of an operating system from the seventies. My problems with Windows are the following: the unfortunate accident of the VMS pathnames. The unforunate accident of drive letters. Through an accident of history, it doesn’t fit with the C language. Also, Control-C should have singled an event object. It should not create a new thread.
I know this is quite an old post now but it seems the most appropriate one to reply to. Your posts used to show up regularly on time, practically every day (it was 3pm for me except on days between DST transitions (as in, my DST transition has happened this year, yours hasn’t, or vice versa)).
But since the move, they don’t seem to be showing up at the same time. Have you lost the ability to schedule your posts or does it not give you fine grain control over the exact timings?
Scheduling is not working. Even automated posting is not working. (The XML-RPC endpoint accepts the post but does not publish it.) Must be done manually. The server folks are investigating.
Comments used to auto-close 2 weeks after a post was posted; if this comment is submitted successfully, then it seems that’s no longer the case.