If you run TFSDeployer.exe with the -d switch it will run in console mode, it can be easier to spot unhandled exceptions in this configuration. usually it is some configuration glitch or some security glitch.

The base address setting is the address that TFS will call TFS Deployer on when a build quality status is changed.

Some clarification would be good here as it looks like this is where my TfsDeployer is falling over.

I got it up and running today and I’m impressed. This is a great demonstration of TFS being extended… it was also a great excuse to get into powershell

One thing that would be useful is more diagnostic messages when they service fails to start. I didn’t see anything in the event log or the working dir

Thanks everyone for the work on this and especially for open sourcing it

I checked the event subscription and found the service availabale, but also get the below error.
Can Anyone throw some light on it

http://:8899/BuildStatusChangeEvent/BuildStatusChangeEvent
=============================================
-
-
-
a:ActionNotSupported
The message with Action ” cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).