Various ways to Deploy SharePoint WebParts

 There are several ways to deploy Webparts

Method 1 - manual

• Copy assembly DLL to either
  - /bin directory for a given IIS virtual server (e.g., c:\inetpub\wwwroot\bin)
  - Global Assembly Cache (e.g., c:\windows\assembly)
• Copy DWP file to C:\Inetpub\wwwroot\wpcatalog
• Copy resources to
  - For GAC-registered parts, C:\Program Files\Common Files\Microsoft Shared\web server extensions\wpresources
  - For Web Parts in the /bin directory, C:\Inetpub\wwwroot\wpresources
• Adjust web.config
  - Register as SafeControl
  - Select Code Access Security settings

Method 2: CAB File

• CAB file should contain
  -Assembly DLL
  -DWP file(s)
  -Manifest.XML
  -Resource files (if needed)
• CAB won't contain
  - Code Access Security settings
• Server-side object model has methods for deploying such a CAB file
• Deploy with STSADM.EXE
  Located in C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN
  Add it to your path
  Stsadm -o addwppack -filename filename [-globalinstall] [-force]

Method 3: MSI File via WPPackager

• All of the features of CAB file deployment, but with
  - Code Access Security support
  - Ability to uninstall via Control Panel
• Get WPPackager.exe
• Add additional files to project for use by WPPackager
• Run WPPackager after project is built

Sharepoint Tips & Tricks

1. Deleting error occurred webparts in the portal

  If an error occurs like “An unexpected error has occurred.” and unable to open the design page and the aspx page in the site then follow the below step.

This can be done by adding “?contents=1” to default.aspx page.

 ex: http://myportal/default.aspx?contents=1


2. Adding Quick Launch to Custom webpart Pages


   To  display quick launch bar in Custom web part pages, all you need to do is simply remove couple of lines in the web part page by opening the page in the Designer.

<asp:Content ContentPlaceHolderId="PlaceHolderPageImage" runat="server"></asp:Content>
<asp:Content ContentPlaceHolderId="PlaceHolderLeftNavBar" runat="server"></asp:Content>
<asp:Content ContentPlaceHolderId="PlaceHolderNavSpacer" runat="server"></asp:Content>

Configuring host header for site in IIS 7.0

 

You can perform this procedure by using the user interface (UI), by running Appcmd.exe commands in a command-line window, by editing configuration files directly, or by writing WMI scripts.

User Interface

To use the UI

1. Open IIS Manager. For information about opening IIS Manager, see Open IIS Manager (IIS 7).
2. In the Connections pane, expand the Sites node in the tree, and then select the site for which you want to configure a host header.
3. In the Actions pane, click Bindings.
4. In the Site Bindings dialog box, select the binding for which you want to add a host header and then click Edit or click Add to add a new binding with a host header.
5. In the Host name box, type a host header for the site, such as www.contoso.com.
6. Click OK.
7. To add an additional host header, create a new binding with the same IP address and port, and the new host header. Repeat for each host header that you want to use this IP address and port.

Command Line

To add a host header to a Web site's binding, use the following syntax:
appcmd set site /site.name: string /bindings.[protocol=' string ',bindingInformation=' string '].bindingInformation: string
The variable site.name string is name of the site to which you want to add a host header. The variable [protocol='string',bindingInformation='string'] is the existing binding to which you want to add a host header, and bindingInformation string is the new binding with host header.
For example, to configure a site named contoso with an existing HTTPS binding for all IP addresses, on port 443, without a host header to have a host header named marketing, type the following at the command prompt, and then press ENTER:
appcmd set site /site.name: contoso /bindings.[protocol='https',bindingInformation='*:443:'].bindingInformation:*:443: marketing
For more information about Appcmd.exe, see Appcmd.exe (IIS 7).

Configuration

The procedure in this topic affects the following configuration elements:
<bindings> under <site> element