Instructional video demonstrations for how to use Windows Live Writer are now available.  Check them out on Soapbox and YouTube!

1 – Getting Started

2 minutes, 26 seconds
This instructional video demonstration shows how to setup Windows Live Writer to work with your blog and, if you don't already have a blog, how to create a new blog on Windows Live.

2 - Basic Authoring

2 minutes, 16 seconds
This instructional video demonstration shows how to do basic authoring of a blog post using Windows Live Writer.

3 - Pictures, Videos, Maps and Plug-ins (oh my!)

5 minutes
This instructional video demonstration shows how to insert and edit rich content - like pictures, videos and maps - using Windows Live Writer.

4 – Open, Save, Publish and Help

2 minutes, 44 seconds
This instructional video demonstration shows how to open, save, print and publish blog posts using Windows Live Writer. You will also learn about how to get more information and send feedback to the Windows Live Writer team.

5 - Windows Live Writer

11 minutes
This is a single video that covers the all the same content in the videos listed above (1 - 4).

Enjoy!

For those of you who frequently include images in your blog posts and find that you often apply the same settings, there is a convenient feature in Writer that enables you to save those settings as the defaults for all future images. 

How it works

• First, inset an image. 
• Then apply the settings to the image so it look the way you want (for example: change the text wrapping to "Right" and apply the "Photopaper" border).
• Then click on the "Save settings as default" link at the bottom of the Image Properties sidebar (as shown on the right).

Now, the next time you insert an image it will be using the settings that you just saved following the steps above.

Settings that get saved

Not all settings get saved when you use this feature.  Settings that will be saved are:

• Text wrapping
• Margins
• Borders
• Link to
• Image size
• Watermark effect

Defaults per blog account

The defaults are saved uniquely for each blog account.  That means if you have Writer configured to multiple blog accounts you can specify settings for images that are unique to each account. 

Revert to default settings

And for those of you who tend to get a little crazy formatting your images and take it a little to far, it's easy to wipe the slate clean and start over by clicking "Revert to default settings" at the bottom on the Image Properties sidebar.  This will remove any changes that you've applied to the image and set it back to whatever the images defaults are for that account.

Get back to the defaults that came with Writer

If you changed the image setting defaults for your account and want to change them back to the defaults used by Writer do the following:

• Set "Text wrapping" to "Left"
• Set "Margins" to "No Margins"
• Set "Borders" to "Drop Shadow"
• Set "Link to" to "Source"
• Set "Image size" to "Small"
• Remove any watermark effects
• Click "Save settings as default"

Here's some live footage from the Microsoft Windows Experience Lounge during the 2008 BlogHer Business Conference.  Thanks Sara Ford!!

One correction to the video: Writer is not in Beta anymore.  You can install the official "out of beta" version at http://writer.live.com/.

Live From the Microsoft Windows Experience Lounge

The Picasa Data API newsgroup has reported they have fixed the issue that was causing posts that contain images to not publish on Blogger (thanks Jeff Fisher for the quick response!).  We have verified that the fix does addresses the issue Writer was having publishing to Blogger.

If you continue to have problems with Writer please post on our newsgroup.

Thanks to everyone for their patience and sorry for the inconvenience.

Today, the Writer team learned of changes to Blogger that cause Writer to fail when publishing posts that contain images.  When attempting to publish a post that contains images, Writer will show the following message:

We're currently investigating a fix for this issue and will post an update as soon as we have more information.

Thanks to everyone who reported this issue.