TL;DR; Refactoring a TFS Event Handler to use MSMQ, splitting it into modular services for event queuing and handling, improving maintainability and administration.

I am half way through the MSMQ Refactor of my TFS Event Handler project and thing are starting to come together. I have changed it so that instead of one big solution I will have three smaller ones. This will allow me to cross reference the different services.
Essentially the Team Server fires events that a service (TFSEventQueuer) captures and adds them, with a little jiggery porkery, to a message queue. The second service (TFSEventHandlers) reads the Queue and executes the appropriate handlers.
This should be pretty neat once it is complete, and the interface should allow users to easily administer the handlers.
Still a long way to go… But I hope to have a working version by the end of the week…
Technorati Tags: WIT
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.

Cognizant Microsoft Business Group (MBG)

Schlumberger

Alignment Healthcare
NIT A/S

MacDonald Humfrey (Automation) Ltd.

Slaughter and May

ProgramUtvikling

Deliotte

Philips

Akaditi

Workday

Sage

Higher Education Statistics Agency

Brandes Investment Partners L.P.

Flowmaster (a Mentor Graphics Company)

Lockheed Martin

Illumina

Emerson Process Management

New Hampshire Supreme Court

Washington Department of Transport

Washington Department of Enterprise Services

Ghana Police Service

Department of Work and Pensions (UK)

Nottingham County Council

Slaughter and May

Freadom

Brandes Investment Partners L.P.

Kongsberg Maritime

Sage

Slicedbread