Task 1: Ensure code service is running
1. Click Start, then click Administrative Tools, and then click Services.
2. Right-click SharePoint 2010 User Code Host, and then click Properties.
3. Verify that the service is not started, and that the Startup type is Disabled.
4. Click OK.
5. Open SharePoint 2010 Central Administration.
The User Account Control dialog box appears.
6. Click Yes.
7. In the Quick Launch, click System Settings.
8. Click Manage services on server.
9. In the Microsoft SharePoint Foundation Sandboxed Code Service row, click Start.
The service status changes to Started.
10. Switch to the Services console.
11. Right-click SharePoint 2010 User Code Host, and then click Properties.
12. Verify that the service is started, and that the Startup type is Automatic.
13. Click OK.
14. Close the Services console.
Task 2: Upload a sandboxed solution
1. Switch to Internet Explorer.
2. In the address bar, type http://intranet.contoso.com/sites/IT, and then press
3. Click Site Actions, and then click Site Settings.
4. In the Galleries section, click Solutions.
5. In the Ribbon, click the Solutions tab, and then click Upload Solution.
6. Click Browse.
7. Select D:\Labfiles\Lab07\BadReceiver.wsp.
8. Click Open.
9. Click OK.
10. In the Ribbon, click Activate.
The BadReceiversolution is displayed with a status of Activated.
11. Click Site Actions, and then click Site Settings.
12. In the Site Actions section, click Manage site features.
13. In the BadReceiver Feature1 row, click Activate.
Task 3: Test a sandboxed solution
1. In the Quick Launch, click All Site Content.
2. Click Announcements.
3. In the Ribbon, click the Items tab.
4. Click New Item.
5. In the Title box, type My Announcement.
6. Click Save.
An error message appears.
7. Click Go back to site.
8. Click Site Actions, and then click Site Settings.
9. In the Galleries section, click Solutions.
Observe that the BadReceiver solution shows no resource usage. That is
because the timer job has not yet calculated resource usage for the solution.
If you happen to see resource usage, then you were lucky! The timer jobs executed just in time.
Results: After this exercise, you should have deployed and tested the BadReceiver solution.