I have just released a new version of the TFS Event Handler. This is a really rough version and you should not be used in a production environment.
Event handler system will work in this version, but a manual config is required, and the user interface is a bit flaky. Also all errors that occur in an individual handlers are ignored.
If you are planning to use this in a production environment please consider using the TFS Event Handler (Prototype) .
I will probably not be doing any documentation for this version, but I will be updating frequently as I will be using it on my production server and building Event handlers for it.
The Client application allows you to connect to any TFS Event Handler and see what the status is. Please note that there is a bug that occurs when you add a new team server that means that it never authenticates. Once you have added it, close the UI and reopen it to solve the problem. Oh, and don’t click the “refresh” button (I said the UI was rough).
It will take time to augment the UI and I have quite a few ideas in that regard. One of my goals is to allow the upload of “Packages” that contain all the files necessary to run en Event Handler that might well have supporting files, like html templates for emails…
At the moment the server component runs in a form, but that will eventually be a service.
Hopefully buy the end of next week I will have a version of the service stable enough to run as a service, and a version of the UI integrated with Visual Studio 2008.
Well, that’s the plan… 
Edited for bad English and down right sloppiness… Made me sound like English was not my first language…
Technorati Tags: .NET ALM WIT VS 2008
What to read next
TFS Event Handler (Prototype) Refresh
Bug fixes and updates for the TFS Event Handler Prototype, now supporting .NET 3.5 and Visual Studio 2008. Includes installer refresh and …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …