Windows Live Writer: Known Issue

Windows Live Writer: Known Issue

  • Comments 2

Let me save you some time if I can with a known issue in the Writer beta.  Doh!  My previous post, which just got posted moments before this one, was actually finished earlier this morning.  When I hit the Publish button, I received the following error:

Windows Live Writer Error

"Blog Server Error: Server Error 0 Occurred - Object reference not set to an instance of an object."

I tried opening/closing Writer, but kept getting the same error.  I thought, "Uh oh, this can't be good!" 

Well, after posting the error on one of our internal mailing lists, I got a quick response.  It turns out that this was caused by a known issue in the current beta build 1.0 (109).  In my previous post, I mentioned how I accidentally hit the Publish button half way through and it ended up going live on my blog for a short time.  Since Writer doesn't have a "Delete Post" button (at least none that I saw at the time), I manually deleted the post using the manage settings UI in Community Server.  That's where I ran into my problem...

From Spike on the WL Writer team:

There is a known bug with deleting a posted entry that is currently open in Writer.  The problem is that we have an ID associated with that post, and so we try to send an update command to the blog service, but since that ID no longer exists, you get an error.

If you have multiple blogs configured, in the post window, you can switch to another blog, and then back to the blog you want and that will cause the Writer to drop the post ID information so you can re-publish as a new post.

-Spike

I went back into Writer and attempted the workaround by connecting Writer to my personal blog on Windows Live Spaces.  I toggled between my personal & work blogs, then attempted to re-post.  This time, when I hit the publish button, everything worked, and you see the previous post perfectly!

  • I haven't tried Windows Live Writer personally, but there's one thing about this screenshot that is making me shake my head in disappointment.

    The red X icon.

    Some designer on the Windows Live team decided that Windows Live Writer should NOT use the standard Windows "red X" icon, but should use its own.  That designer then proceeded to spend time (or, have someone else spend their time) drawing an icon.

    WHY?!

    Windows comes with a perfectly good red X icon.  You load it using LoadIcon(NULL, IDI_ERROR).  This has been around since at least Windows 3.1.  The good thing about using the built-in icon is that you get an optimal experience regardless of what OS you are running: XP has an XP-style icon, Vista has a Vista-style icon, 95 has a 95-style icon, etc.  Why should a user see one red X icon from 99% of their Windows apps (e.g. everytime they use MessageBox with MB_ICONERROR), but a different one within Windows Live Writer?

    This may seem like just one small, minor issue.  But it is an example of a growing, disturbing trend at Microsoft: apps going against UI guidelines, apps re-inventing the wheel provided by the OS platform, for no good reason.
  • For those who have notyet experienced this error while using Window Live Writer, hopefully this will

Page 1 of 1 (2 items)