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.
Brandes Investment Partners L.P.
Milliman
YearUp.org
Epic Games
Trayport
SuperControl
Jack Links
Graham & Brown
Flowmaster (a Mentor Graphics Company)
Xceptor - Process and Data Automation
Sage
ALS Life Sciences
Slaughter and May
Akaditi
Microsoft
NIT A/S
Slicedbread
DFDS
Washington Department of Enterprise Services
Department of Work and Pensions (UK)
Nottingham County Council
New Hampshire Supreme Court
Royal Air Force
Ghana Police Service
Genus Breeding Ltd
Epic Games
Lean SA
Capita Secure Information Solutions Ltd
MacDonald Humfrey (Automation) Ltd.
Boeing