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.

Jack Links

Qualco

DFDS
NIT A/S

MacDonald Humfrey (Automation) Ltd.

Akaditi

ProgramUtvikling

Healthgrades

Alignment Healthcare

Microsoft

SuperControl

Kongsberg Maritime

Slaughter and May

ALS Life Sciences

Xceptor - Process and Data Automation

Cognizant Microsoft Business Group (MBG)

Big Data for Humans
Boxit Document Solutions

Washington Department of Enterprise Services

Royal Air Force

Department of Work and Pensions (UK)

Washington Department of Transport

New Hampshire Supreme Court

Nottingham County Council
Boxit Document Solutions

Hubtel Ghana
CR2

Illumina

Genus Breeding Ltd

Schlumberger