Set a breakpoint on the public Service class constructor and step through the code when something is checked in.

Make sure your locals and callstack windows are open (Debug > Windows).

I'm happy to help further (as I'm sure Rendle, Kenny et al will be too) if needed.

Cheers. Now that I've been away for the night and come back to it I've got somewhere... and it's a pretty simple mistake.

The ASP.NET development server only allows connections from localhost. I think this is causing the problem, as the publishing server (which is actually on localhost) is getting connection refused errors.

I can copy the service over to a machine with IIS, but then I won't have any access to the debugging stuff, right? Can I get it to log into a file or something?

It looks it.

I'm OK for now, though- I found some error logs that were complaining about access- once I'd changed a few permissions it was all up and running and writing to my test file. Now I just need to do some jiggery pokery and get it to update a database...