I use Executor (http://executor.dk) and love it. Well, most of the time I do. Every once in a while it seems to freak out and looses all of it’s settings including keywords. Loosing the setting are no big deal, but the keywords?
I have use various methods to resolve this in the past, remove and re-install etc. Last week it happened again. Removing and re-installing did not help at all, it just looked blank.
Executor does such a great job of just working in the background and requires very little attention I had not explored it’s vast features. Well, this time I found that all of the default keywords could be restored by importing them from the original files that were used during install.
On the keywords tab context menu is “Import keyword from file…” which allowed me to import see the standard.exc which was all the missing keyword AND a windowskeywords.exc with added some I did have before.
I also noticed a “Export keywords..” with once I had them all setup the way I wanted I promptly used to export them all to a file of my choosing to make it easier to fix next time.
“Import from start-menu…” also looks very interesting and I am sure will save me some typing in the future.
I have been keeping my source control in Team Foundation Server for years, but have faultered when it comes to using Work Items. Oh, I have tried a few time and then stopped for various reasons. Today I thought it would be good to clean up the old work items and try again. This turned out to be a bit of an issue. There is not right-click delete, selection all and then choose delete from the action menu.
So how do you delete a Work Item?
I finally found it the WitAdmin command line tool, part if the Team Foundation Server Power Tools, allows you to destroy work items by id.
Usage: witadmin destroy /collection: collectionUrl /id: id
Example: witadmin destory /collection:http://tfs.example.com:8080/DefaultCollection /id:112345
This allowed me to delete the work items, good thing was that I didn't have that many to delete.
Since I am the build manager for my team and have to touch every release I get a lot of files on my hard drive that I don’t need anymore. I mean when we are on release 15.2 do I really need a local copy of release 8 or 10, or 14 for that matter. I used to just delete the local copies, but TFS still thinks you have them and starts acting up. Of course there is a way to delete them via Source Control Explorer but it is not very obvious. I found the solution on a post titled “TFS Top Tip #11 –Removing source control files from your local file system” by Martin Woodard.
It appears that if you do a Get Specific Version and specify Changeset of 1 the files will be deleted locally and the server will know it. Changeset 1 is a special Changeset that only contains the root ($/). So by getting Changeset 1 you basically get nothing, there were no files in the source control tree when this Changeset was created.
This is definitely not as easy a deleting a branch in git, but I does help me keep my release folders cleaned up. Thanks Martin for posting this.
Recently I need to do a couple of things programmatically for a build task and wanted catalog the command to make it easier for me and others to find them in the future.
Clear Internet Explorer Cache
C:\Windows\System32\rundll32.exe InetCpl.cpl,ClearMyTracksByProcess 8
Clear The Windows Clipboard
This one I came across when trying to figure out why cut/paste operations on my install of Windows 7 is so slow. Unfortunately this didn’t speed up the clipboard but I wanted to keep it around anyway. Comes in handy when I forget to clear a photo or large document from the clipboard. Here is the command.
cmd.exe /c “echo off | clip”
Do you have a command/snip-it that helps you get things done? Share them in the comments.
My buddy, Shawn, over at UserGroup.tv as hanging out at the Northwest Arkansas TechFest this year and he videoed on my my talks. The one on Highway.Data. Highway.Data is an abstraction layer of Entity Framework (and soon Nhibernate) that makes working with data access much easier. It’s built in repository, unit of work and query specification really bring EF, or any ORM for that matter, to a well rounded tool for you tool belt.
This is the second video for me on UserGroup.tv and thanks to Shawn for hosting them. You can check out the videos of other presentations by me and others by going to UserGroup.tv.