tfs – using winmerge as your merge/diff tool
If you're used to using something like winmerge with your SCM of choice, if you wind up using TFS, the built-in diff/merge tools can leave much to be desired.
Here is how to change the tool VS 2kX uses to do diffs/merges when hooked up to TFS (note that these are my settings for using winmerge for ALL file types):
Go To: Tools/Options/SourceControl/Visual Studio Team Foundation Server/Configure User Tools
Click "Add..."
Extension: .*
Operation: Compare
Command: C:\Program Files\WinMerge\WinMergeU.exe
Arguments: /e /wl /dl %6 /dr %7 %1 %2
Click "Add..."
Extension: .*
Operation: Merge
Command: C:\Program Files\WinMerge\WinMergeU.exe
Arguments: /ub /dl %6 /dr %7 %1 %2 %4
The winmerge command line reference can be found here.
tfs – error exporting queries to excel
Starting my new project in a new role, as project lead, I need to be managing things in TFS. The UI for batching these things up is nonexistent, but there is Excel integration so you can do it all in Excel, hit save, and it all goes back to the TFS server... pretty slick I must say (I was actually in the midst of writing such a tool when I realized this functionality already existed OOB).
However, the first time I tried to use this functionality... BLAM, I get smacked with this:
TF80042: The document cannot be opened because you do not have Microsoft Excel 2003 or later, or one of its components installed. For more information, see the Team Foundation Installation Guide.
Isn't that teh suck?
Anyways, there is a sweet write-up on how to fix it here: http://blogs.microsoft.co.il/blogs/srlteam/archive/2007/07/17/Error-when-trying-to-export-queries-to-Excel.aspx.
Thanks Elad!
Going Medieval on Your App with Castle MonoRail – Indy ALT.NET
So last night I gave a talk at Indy ALT.NET on Castle MonoRail. It was really just a sort of intro to MonoRail type of deal, but the cool part was that we held a Dojo after I got done jabbering.
We ended up building a Poll Generator for our dojo activity. We almost got done in the 45 minutes or so that we dojo'd. It was a pretty fun activity, and I'd like to do it again sometime soon.
Also, this was really my first public speaking engagement to our technical community, and let me say it was a blast. Everyone had great things to say, and many great questions were asked too.
I set up a google code repository so you can grab my slidedeck and grab the source for our dojo activity and my demo app.
Maybe next time I'll post before the talk, so I can let people know about it.
Thanks guys for all the great feedback, and thanks to my wife for understanding why I wasn't spending any of my evenings with her this week!
singly implemented interface… addendum
Wowza! So I've begun reading LosTechies (tons of great content, highly recommended!), and came across a passage today from Jimmy Bogard, who says what I feel, but what I couldn't get out of my head:
On a sidenote, it always bothered me when people say that an interface with one implementation is a design smell. No, an interface is used to expose a contract. Interfaces communicate design intent, far better than a class might.
Exactly!
