Missing TortoiseSVN Shell Icon overlays

This has been bugging me for weeks and today I finally found and resolved the problem so thought I should share in case anyone else has this problem too.

I couldn’t remember when I first noticed they were missing but when ever I checked a working folder on my laptop the tortoise svn icon overlays were missing. When I edited a file the red cross would appear as expected, but the green tick to say a file was up to date or the question mark for non-versioned files were missing, meaning I didn’t know if a file was up to date with the repo head or an ignored/non-versioned file.

This morning I came across a post on stack overflow that suggested modifying the registry to over-right the usual Microsoft default setting cock-up. In Windows, for memory reasons Im guessing, they have limited the number of allowed Shell Icon overlays  to 11. Now at first this seems like a logical way to stop memory abuse in Explorer. But for some stupid reason (most likely so their overlays come first), they are actioned in alphabetical order, so any overlays in position 12+ are ignored. With M being in the middle of the alphabet this results in the majority of these slots being allocated by Microsoft Products. In this case Tortoise SVN (obviously starting with a T) was being pushed out of the allowed slots.

I found this out by doing a search in the registry for ‘ShellIconOverlayIdentifiers’  (NOTE: only open regedit if your comfortable using it, we don’t need to change anything just taking a peek so you should be ok). This reviled that most of the Shell Icon slots were being taken up by something called Microsoft Groove. Not having a clue what this is I turned to a popular search engine to find out.

Microsoft Groove is the name for their multi-user document collaboration tool, which makes sense that it would need some icon overlays as it is essentially the same thing as Tortoise SVN. I don’t do any online document collaboration so re-searched for how to remove it. The Microsoft knowledge base article advised to remove the feature from Office via the add/remove programs control panel but when I looked I couldn’t find anything that mentioned Groove but after a further search or two I found that it has now been renamed to Microsoft SharePoint Workspace, which was listed in my version of Office. I disabled the feature and restarted my laptop and I now have my overlay icons back.

™

What happened to the design?

Today, one or two of you may notice the site looks a little different. That’s because the style sheets for both my site and the blog have been removed for one international day (that’s about 48 hours to you and me) to celebrate CSS Naked Day.

Every year, website developers across the world remove their style-sheets and show off their <body> to help promote web standards. Its a great opportunity to double check and show people that your website is written for and accessible to all.

To know more about why styles are disabled on this website visit the Annual CSS Naked Day website for more information.

Verify your domain via DNS

Google have announce another way to verify you own a domain in their webmaster tools, via a DNS TXT record.
This solves a problem I have had many times in that it verifies the whole domain.

Until now, you had to verify you owned every sub-domain on a domain before you could use webmaster tools for it, while for most sites this is fine, you verify the www. version, sometimes there are a couple more that need to be done.
for example on my site, I use the non-www domain, also there is a dev. and a api. that also need their own verification meta tag/html file. If I want to use webmaster tools on another sub-domain I have to verify again… this becomes a tiresome process.

Enter the new DNS verification. You now add a TXT record to your dns and it automatically covers any sub-domains you add.
That’s it… done! There is of course the usual dns propagation you have to worry about so it may not be a quick as adding a meta tag, but it defiantly saves time in the long run.

You can find out more by visiting the Google Web master tools or popping over to the Webmaster Central blog.