Be careful creating custom subscriptions with BisSubscribe - event type names are case sensitive

Published 16 March 06 09:01 AM | psheill 

We tried to be generally case insensitive in Tfs, in alignment with the default settings in Sql Server and Windows.  There's one place where we messed up though.  If you create a subscription to a "CheckInEvent" through the command-line tool, you won't get any alerts.  That's because the event type is really "CheckinEvent" -- small 'i'.  We do the type matching based on a hashtable lookup, and the hashcode for "CheckinEvent" is different from the hashcode for "CheckInEvent".  The unfortunate result is that you won't receive any notifications.  We will certainly fix it in the next version.  Until then, be careful.

 

Comments

# Team System News said on March 20, 2006 9:14 AM:
Jeff Beehler says Team Foundation Server Ships!  And so does John Lawrence, complete with a picture of...
# Naren's Blog said on July 26, 2006 7:20 PM:

I was collecting links & pointers to answer common questions in forums related to TFS eventing...
# Naren's Blog said on October 12, 2006 8:16 PM:

I was collecting links & pointers to answer common questions in forums related to TFS eventing and

# SRLTeam said on November 10, 2006 2:25 AM:

Team System has a built-in, extendable alerting mechanism. It is based on SQL Server 2005 Notification

New Comments to this post are disabled
Page view tracker