Manual Installation and Removal

These instructions are only for older versions before v2.8 - please see this page for Installation for version 2.8+

  • To install the Web Part on to SharePoint manually first install using the Manual option to obtain the Web Part CAB and WSP files.

 

 

 

 

 

 

  • The Web Part CAB and WSP files are then available in the Web Part Files folder in the programs installation directory

  • SharePoint 2010

The web part should be installed using the Pentalogic.SharePointPlanner.WSP file.

This example shows how to add the solution file and then deploy it to all sites on a local server using STSADM :-

    SET PATH=%PATH%;"c:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN\"

    CD "C:\Program Files\Pentalogic\SharePoint Planner 2\Web Part Files"

    STSADM.EXE -o AddSolution -filename Pentalogic.SharePointPlanner2.wsp

    STSADM.EXE -o DeploySolution -name Pentalogic.SharePointPlanner2.wsp -allcontenturls -immediate -force -allowCasPolicies

    STSADM.EXE -o execadmsvcjobs

This example shows how to retract and then delete the solution file :-

    SET PATH=%PATH%;"c:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN\"

    STSADM.EXE -o RetractSolution -name Pentalogic.SharePointPlanner2.wsp -allcontenturls -immediate

    STSADM.EXE -o execadmsvcjobs

    STSADM.EXE -o DeleteSolution -name Pentalogic.SharePointPlanner2.wsp -override

For more information on how to install the web part on a server farm or to individual sites please consult the SharePoint documentation.

The above commands will install the web part to the servers BIN directory and automatically setup the Code Access Security (CAS) permissions as detailed above.

(Note - due to limitations in SharePoints deployment facility you must manually deploy the French language resource file Pentalogic.SharePointPlanner2.resources.dll when performing a BIN directory install if you wish to use the French language localization)

 
  • WSSv3 or Microsoft Office SharePoint Server 2007

The web part should be installed using the Pentalogic.SharePointPlanner.WSP file.

This example shows how to add the solution file and then deploy it to all sites on a local server using STSADM :-

    SET PATH=%PATH%;"c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\"

    CD "C:\Program Files\Pentalogic\SharePoint Planner 2\Web Part Files"

    STSADM.EXE -o AddSolution -filename Pentalogic.SharePointPlanner2.wsp

    STSADM.EXE -o DeploySolution -name Pentalogic.SharePointPlanner2.wsp -allcontenturls -immediate -force -allowCasPolicies

    STSADM.EXE -o execadmsvcjobs

This example shows how to retract and then delete the solution file :-

    SET PATH=%PATH%;"c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\"

    STSADM.EXE -o RetractSolution -name Pentalogic.SharePointPlanner2.wsp -allcontenturls -immediate

    STSADM.EXE -o execadmsvcjobs

    STSADM.EXE -o DeleteSolution -name Pentalogic.SharePointPlanner2.wsp -override

For more information on how to install the web part on a server farm or to individual sites please consult the SharePoint documentation.

The above commands will install the web part to the servers BIN directory and automatically setup the Code Access Security (CAS) permissions as detailed above.

(Note - due to limitations in SharePoints deployment facility you must manually deploy the French language resource file Pentalogic.SharePointPlanner2.resources.dll when performing a BIN directory install if you wish to use the French language localization)

 
  • WSSv2 or SharePoint Portal Server 2003

The web part and its associated files are stored in Pentalogic.SharePointPlanner2.CAB and a SharePoint Administrator may chose to perform an installation using the STSADM tool or another SharePoint Administration tool.

To install using STSADM execute the following command

    SET PATH=%PATH%;"c:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN\"

    CD "C:\Program Files\Pentalogic\sharePoint Planner\Web Part Files"

    STSADM.EXE -o addwppack -filename Pentalogic.SharePointPlanner2.cab -globalinstall

to remove

    SET PATH=%PATH%;"c:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN\"

    STSADM.EXE -o deletewppack -name Pentalogic.SharePointPlanner2.cab

Installing to individual sites

If you wish to install the web part to a specific virtual server, you should use the -url option in addition to -globalinstall. The STSADM documentation is a little misleading, -globalinstall actually installs the web part into the Global Assembly Cache (GAC) which is necessary for it to function correctly. If you include the -url parameter it does not install the web part dwp file into every virtual servers web part gallery but only those you specify.

    STSADM -o addwppack -filename Pentalogic.SharePointPlanner2.cab -url http://<yourvirtualserve> -globalinstall -force

CAS Settings

The web part requires the following permission set to operate.

It is highly recommended that you install web part into the Global Assembly Cache (GAC) using the -globalinstall option as then you will NOT need to manually edit your web.config files to add the following permission set :-

<PermissionSet class="NamedPermissionSet" version="1" Description="Minimum permission set for Pentalogic World Time web part to run">
<IPermission class="System.Web.AspNetHostingPermission, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1" Level="Minimal" />
<IPermission class="System.Security.Permissions.SecurityPermission, mscorlib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1" Flags="Execution" />
<IPermission class="Microsoft.SharePoint.Security.WebPartPermission, Microsoft.SharePoint.Security, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
version="1" Connections="True" />
<IPermission class="Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
version="1" ObjectModel="True" />
</PermissionSet>