0

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?

Improve this question
2
  • 1
    Nothing change in 2013. Did you restart the Timer Service after performing the deploy.
    – Marco
    Jul 1, 2016 at 15:03
  • @Marco can you add that as an answer?
    – Zach
    Jul 1, 2016 at 18:22

1 Answer 1

Reset to default
0

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

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.