Administrator Guide

Update Procedure

The Flex Update package typically contains updated Web parts (WSP files), a Batch file (which is a set of commands that update and deploy the included Web parts) and may also contain a Template file (Flex template.stp).

To install the Update:

  1. Unpack the zip file. Run the batch file included.
  2. The process will ask for the site to update, enter the URL (or http://site:port#) or leave it blank for all universal deployment –however, see note #2 below.

IMPORTANT NOTES:

  1. WARNING: This update will shut down IIS during this process. Always do a backup of your site before proceeding.
  2. The Update process replaces the current Web Parts in the Solution Store and deploys those Web Parts to the Target site specified – Note: If the Target site is not specified during the initial running of the batch file, the deployment will be universal and Web Parts that have no reason to be deployed in non-Flex sites will populate their BIN folder and update the “safe controls” section of that site’s Web config file.
  3. The process copies the Web Parts to the bin folder and the GAC during the deployment phase of the specified site.
  4. Then Webconfig’s “Safe Control” section is updated with the necessary entries to allow the new or updated Web Parts to function properly in Flex application.
  5. If multiple Web Part deployment (or for some reason the automated batch file system did not deploy the Web Parts provided then a manual deployment will have to be done via the SharePoint Solution Deployment Administration interface.
  6. The actual site definition itself, which is defined as the data and its lists/columns will NOT be affected.

The new Web Parts will update the corresponding Web Parts in the SharePoint Solution Store and then redeploy these updated Web Parts to the bin folder and/or the GAC (and also update the Web.config file accordingly).

The Flex Template file replaces the previous Flex Template file in the SharePoint Solution Store but does nothing else. In other words, the Template itself does not replace the current site or sub-site designated as your Flex solution.

 

Was this helpful?