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.

Slaughter and May

Akaditi

DFDS

New Signature

Flowmaster (a Mentor Graphics Company)

Higher Education Statistics Agency
NIT A/S

Trayport

Big Data for Humans

Qualco

Illumina
Boxit Document Solutions

Emerson Process Management

Milliman

Sage

Slicedbread

Graham & Brown
CR2

Royal Air Force

Washington Department of Transport

Department of Work and Pensions (UK)

Washington Department of Enterprise Services

Nottingham County Council

New Hampshire Supreme Court
NIT A/S

Kongsberg Maritime

Microsoft

Lockheed Martin

Flowmaster (a Mentor Graphics Company)

New Signature