Hi all,
I've a custom timer job that reads from a web service to synchronize metadata in a document library against the web service content. I define what specific document library by reading from the secure store service where I store the URL/PATH/LIBRARY NAME values.
In the past, I would debug this solution attaching to owstimer and manually run the timer job and catch breakpoints and view the data on the stack and what not.
As of a few days ago, this is no longer possible. I've rebooted, restarted the timer service, VS many times over 2 days of trying to debug a flaw in my application. When I activate my solution, I can see it work and my breakpoints are being caught but when I manually run this custom timer job, VS chugs for a bit and hangs. Nothing happens and none of my breakpoints in the timer job execute override (where the work in a timer job actually gets done) ever get touched. The modifications to my list never happen. It's functionally dead.
Another thing that is confusing (as is the whole web/site/farm/etc deployment model) is that my solution activates (active deployment configuration is set to "No Activation") even though it's not supposed to (should only install and await manual deployment).
Any thoughts?
Paul