TL;DR; Explains using message queues in Team Foundation Server EventHandler to manage events reliably, ensuring no data loss during handler updates or service changes.

As I mentioned in my previous post I am currently building an EventHandler infrastructure for Team Foundation Server .
I am currently toying with the idea of re-engineering to two system services. The first that handles the Team Foundation Server events and puts them onto an event specific message queue and another that handles the reading the messages and action all the event handlers. The reason that I am thinking this way is that when a new EventHandler is added I will need to unload any existing Assemblies and then load them again, and any events that occur during this interval would be lost otherwise.
This can be easily achievable in .NET 3.0 and will not require much work to implement…
If you've made it this far, it's worth a conversation. Tell us where you are and what you're trying to change. Martin reads every inquiry and replies personally.
Start the conversationWe partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.

Flowmaster (a Mentor Graphics Company)

Emerson Process Management

Epic Games

Qualco

Sage

Freadom

Lockheed Martin

Milliman

YearUp.org

MacDonald Humfrey (Automation) Ltd.

Akaditi

ALS Life Sciences

Big Data for Humans

Philips

Brandes Investment Partners L.P.

Trayport

DFDS

New Signature

Washington Department of Enterprise Services

Washington Department of Transport

New Hampshire Supreme Court

Royal Air Force

Nottingham County Council

Department of Work and Pensions (UK)

YearUp.org
CR2

Schlumberger

Capita Secure Information Solutions Ltd

ProgramUtvikling

Flowmaster (a Mentor Graphics Company)