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 connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.

Big Data for Humans

Hubtel Ghana

Philips

Boeing

Lean SA

Freadom
NIT A/S

Capita Secure Information Solutions Ltd

Sage

Trayport

Milliman

Flowmaster (a Mentor Graphics Company)

DFDS

Higher Education Statistics Agency

Epic Games

Emerson Process Management

Workday

Ericson

Ghana Police Service

Department of Work and Pensions (UK)

Royal Air Force

New Hampshire Supreme Court

Washington Department of Enterprise Services

Nottingham County Council

Boeing

Workday

ALS Life Sciences

ProgramUtvikling

Lockheed Martin

Teleplan