More 70-541 links

Deploy a Web service to a Windows SharePoint Services front-end Web server.


Deploy a Web service so that it is available within the context of any Windows SharePoint Services site.

Obtaining the SharePoint Site Context

At run time, if your custom Web service cannot use the GetContextWeb function to obtain the SharePoint site context successfully, you receive the following error message when you try to use the Web service:

System.ArgumentException: Value does not fall within the expected range. At Microsoft.SharePoint.SPSite

When you create a custom Web service for your SharePoint site, you must retrieve an instance of the SPWeb class by invoking the GetContextWebfunction on the SPControl object. To successfully invoke GetContextWeb, your custom Web service must run within the same AppDomain as your SharePoint site. To do this, move your .asmx file to the _vti_bin virtual directory, and move the assembly for the Web service into the _vti_bin/binvirtual directory


Deploy a Web service external to the Windows SharePoint Services context.

Deploying a web service to IIS?

Deploy user controls to a Windows SharePoint Services front-end Web server
Deploy a user control so that it can be used by any Windows SharePoint Services component.


http://sharepointdiaries.com/2009/04/04/70-541-deploy-a-user-control-so-that-it-can-be-used-by-any-windows-sharepoint-services-component/

• Deploy user controls to a Windows SharePoint Services front-end Web server.
• Deploy a user control so that it can be used by any Windows SharePoint Services component.

http://sharepointdiaries.com/2009/04/04/70-541-deploy-a-user-control-so-that-it-can-be-used-by-any-windows-sharepoint-services-component/

Creating Site and Feature Provisioning Components

• Create a feature definition
• Specify a feature that depends on another feature to activate
• Specify an Event Receiver to handle events for a feature
• Localize a feature using a resource file
• Create an action to add an option to the site settings menu
• Add a new master page when a feature is activated
• Cache the master page in a document library

Specify a feature that depends on another feature to activate
http://sharepointdiaries.com/2009/04/04/70-541-specify-a-feature-that-depends-on-another-feature-to-activate/

Specify an Event Receiver to handle events for a feature
http://sharepointdiaries.com/2009/04/08/70-541-specify-an-event-receiver-to-handle-events-for-a-feature/

Localize a feature using a resource file
http://sharepointdiaries.com/2009/04/11/70-541-localize-a-feature-using-a-resource-file/

Create an action to add an option to the site settings menu
http://sharepointdiaries.com/2009/05/19/70-541-create-an-action-to-add-an-option-to-the-site-settings-menu/

Add a new master page when a feature is activated
http://mindsharpblogs.com/pauls/archive/2007/06/18/1903.html

Cache the master page in a document library