210 likes | 306 Views
Packaging and Deploying Web Parts. Agenda. Introduction Building a Web Part Package Creating a Manifest File Creating a . dwp File Creating a .CAB File Using Visual Studio Deploying a Web Part Package Add the Web part to a Web page. Introduction. Prerequisites.
E N D
Agenda Introduction Building a Web Part Package Creating a Manifest File Creating a .dwp File Creating a .CAB File Using Visual Studio Deploying a Web Part Package Add the Web part to a Web page
Introduction Prerequisites • Familiarity with Microsoft Windows SharePoint Services and /or Microsoft Office SharePoint Portal Server 2003 • Knowledge about how to create a Web Part • Familiarity with the Web Part infrastructure
Building a Web Part Package • Manifest.xml (mandatory) • Web Part assemblies (optional) • Class resource files (optional) • .dwp files (optional) A Web Part package is a cabinet (.cab) file that contains the following items:
Reasons to deploy using a solution package Provisioned solution packages will automatically be deployed to new server that are added to the farm. Deploying custom DLL's to the Global Assembly Cache to a remote machine Modifying the web.config on all servers may be pose problems, using a solution package you can very easily modify the web.config especially your safe controls section.
Add the. Web Part project output to the CAB project
Go to Central Administration Tool, under Operations click on Solution Management
Go to the Home page, click Site Actions, and then click Edit age.
At the top of the zone in which you want to display text, click Add a Web Part. In the Add Web Parts to [zone] dialog box, scroll to the Miscellaneous section, select your Web Part check box, and then click Add
It will open a pop up window ,there you can find a web part under Miscellaneous section