How to: Debug a Timer Job
When you create a timer job for Microsoft® SharePoint® 2010, you cannot directly press F5 to debug your code. Instead, you must attach the debugger to the SharePoint 2010 Timer process (Owstimer.exe). This how-to topic describes how to debug a timer job by attaching the Visual Studio debugger to the timer process.
|This how-to topic uses the simple timer job described in How To: Create a Web Application-Scoped Timer Job as an example.|
To debug a timer job in Visual Studio 2010
- On the Start menu, point to Administrative Tools, and then click Services.
- In the Services window, make sure the SharePoint 2010 Timer service is started.
- Open the Visual Studio 2010 project that contains your timer job.
Note: Make sure that the code has not changed since you deployed the timer job; otherwise, the debugger will not match your source code to the deployed assembly.
- Set a breakpoint in the Execute method of your job definition class.
- On the Debug menu, click Attach to Process.
- In the Attach to Process dialog box, click OWSTIMER.EXE, and then click Attach.
- If the Attach Security Warning dialog box is displayed, click Attach.
- In the SharePoint Central Administration Web site, click Monitoring, and then click Review job definitions.
- Click the name of your job, and then click Run Now on the Edit Timer Job page.
- Verify that the Visual Studio 2010 debugger stops execution on your breakpoint.