It has been awhile since I tried to debug a timer job; the last time was on SP2010.
I have a job that updates some values in a list and I want to debug the code. I am attaching to OWSTIMER.EXE and I can see that some of my list values are altered, so I know that it ran, however VS never stops at my break point, which is at the start of the Execute method. The articles I have read, indicate that this should work. Did something change between SP 2013 or there something else I need to do?
-
1Nothing change in 2013. Did you restart the Timer Service after performing the deploy.– MarcoJul 1, 2016 at 15:03
-
@Marco can you add that as an answer?– ZachJul 1, 2016 at 18:22
1 Answer
Nothing change in 2013. Did you restart the Timer Service after performing the deploy?. After every deploy, you have to restart the timer service.
Greetings