Adding a 2nd blog account in Windows Live Writer in Windows 7 gets stuck on “Detecting blog icon”

I’m currently running Windows 7 and I tried to add my 2nd blog account to Windows Live Writer today. Unfortunately, Live Writer would get stuck on the “Detecting blog icon…” message when setting up the new account.

I did a bit of poking around on Google and found a couple of posts about this same issue.

This post mentions that running Live Writer as Administrator fixed the issue for them. (You can do this by right clicking on the Live Writer icon and choosing Run as administrator, btw.) Running live writer as Administrator did not work for me. I still got stuck on the “Detecting blog icon…” message,

This answer from Yahoo Answers mentions trying to close Live Writer and re-open it. Closing and Reopening Live Writer didn’t solve the problem for me. The next suggestion on this question was to reboot windows.

After rebooting Windows 7, I was able to successfully add my 2nd live writer blog account.

Directory "X" associated with feature 'XXX’ in the solution is used by feature 'XXX' installed in the farm. All features must have unique directories

I copy and pasted a feature/module in my VWeWSS solution and updated the module.xml file. Unfortunately, I missed an edit in the file and caused  a problem. After fixing my module.xml file, I got the following error message in visual studio.

“Directory "X" associated with feature ‘GUID1’ in the solution is used by feature ‘GUID2’ installed in the farm. All features must have unique directories to avoid overwriting files.”

This seemed like a straight forward error, but I had a bit of trouble tracking down what exactly to do to be able to use the Deploy command again. I was able to fix the error eventually by retracting my solution. You can retract a solution by performing the following step.

1. Go to Central Administration
2. Click on Operations
3. Click on Solution Management under Global Configuration
4. Click on the name of the problem solution
5. Click on Retract Solution
6. Choose Now for Rectract When?
7. Click OK
8. Wait for the retraction to complete and then try to deploy again from VWeWSS

Hope this can save someone a bit of time.

“Value does not fall within the expected range” when deploying WSP with VSeWSS's deploy command

I started to get a Value does not fall within the expected range error when trying to use the VSeWSS Deploy command from within Visual Studio 2008.

Value does not fall within the expected range.

I spent almost an hour trying to track down what exactly was causing my problem. There are tons of posts about this error message, but it seems like there can be many causes. Unfortunately, none of these solutions worked for me.
After banging my head on my keyboard for a while longer, I started to systematically exclude elements/folders of my VSeWSS project and then trying to run the Deploy command again. Seems desperate, I know, but it ended up helping me find out what exactly was causing this error. Excluding my project Features didn’t fix the error, but by excluding the whole TEMPLATES folder the error went away. I was onto something. I started to exclude sub folders and after playing around with this for a while, I narrowed the problem down to the nav folder within my IMAGES folder. After looking in the folder, the cause was obvious… /Facepalm.

Earlier this morning I had recreated some of my navigation images and replaced the old jpgs with pngs. Unfortunately, my project was still referencing the missing files. By removing the missing references, the error went away. Too bad the error wasn’t a tad-bit more helpful instead of being completely obscure.
In conclusion. If you’re experiencing the Value does not fall within the expected range error. Double-check your VSeWSS project for any references files or folders that no longer exist or any that exist in your folders but are not referenced by your project. Remove any that you find and it might solve your problems.

“A World Wide Web browser, such as Windows Internet Explorer, is required to use this feature” in Microsoft Office SharePoint Designer

In Microsoft Office SharePoint Designer when I Check In a file to my website and choose to Publish a Major Version.

SharePoint Designer shows the following Dialog.

This document requires content approval. Do you want to view or modify its approval status?

When I click Yes, I get the following error dialog.

A world Wide Web browser, such as Windows Internet Explorer, is required to use this feature.

My first instinct was to make Internet Explorer my default browser *shudder*. I did this by opening Internet Explorer, clicking on Tools and selecting Internet Option. I then clicked the Programs tab and clicked on Make Default. Unfortunately, it didn’t make this silly error go away.

A little more digging into the issue presented something interesting. By bringing up Default Programs (Press your Windows Key and enter Default Programs into the search box) and then clicking on Set your default programs, you can see settings for Firefox, Chrome and Internet Explorer web browsers.

By selecting and application on the left, you can set it to be the default program by clicking Set this program as default (clicking this for Internet Explorer didn’t work either, btw) or you can choose some specific defaults for the selected application by clicking on Choose defaults for this program. The latter is basically managing the extensions and protocols associated with the program.

The list of default settings for my web browser are displayed in the 3 images below.

Chrome Associations

Firefox Associations

Internet Explorer 8 Associations

Looking at the differences between the associated extensions, Internet Explorer doesn’t have entries for .shtml, .xht, or .xhtml by default while both Firefox and Chrome do. Thought I’d try to manually associate these three extensions with Internet Explorer to see if it fixed the issue, thinking that one of these extensions was being routed to Firefox or Chrome even with Internet Explorer set to be the default browser. You can do this by going back to Default Programs and clicking on Associate a file type or protocol with a program. Unfortunately, the error wasn’t affected by this change.

To get rid of this error, I actually had to uninstall Firefox and Chrome. I was able to re-install Firefox without checking the Make my default browser checkbox and the error was still gone, but any installation of Chrome would cause the error to come back.

It looks like the only fix for this is to remove Firefox and Chrome if they are installed. If anyone else knows of a valid work-around that allows you to keep Chrome installed, please let me know.

Thanks.