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 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.

MacDonald Humfrey (Automation) Ltd.

Genus Breeding Ltd

Alignment Healthcare

Trayport

Higher Education Statistics Agency

ALS Life Sciences

Lean SA

Illumina

Qualco

Akaditi

Kongsberg Maritime

Healthgrades
CR2

Xceptor - Process and Data Automation

SuperControl

New Signature

Big Data for Humans

Teleplan

Washington Department of Enterprise Services

Washington Department of Transport

Department of Work and Pensions (UK)

Nottingham County Council

New Hampshire Supreme Court

Royal Air Force
NIT A/S

Microsoft

Xceptor - Process and Data Automation

Higher Education Statistics Agency

SuperControl

Genus Breeding Ltd