MCS Build and Release Guide

Note: This is a developer guide.

Pre-Requisites

See Development Notes for details of development environment set-up.

Start with the QA TFS stream.

Create a new TFS branch for the new version.

Ensure that all code has been brought in or created in this stream.

Change the JavaScript and Build versions:

• app.js - change MCS.App.Version to the new version number.
• Web.config - change JSVersion to the new version number.

Ensure that the code builds.

Check in all code changes to the new TFS branch.

Build the Release

Right-click on WebSite.

Select Publish Web App.

• Connection:
  • File System - specify a local target location.
• Settings:
  • Configuration: Release.

Click Publish.

Prep for Release

Copy the local release folder and contents to \\spekefs2012\Projects\Releases\MCS\Release\.

Rename Web.config to Web.config.release.

Rename this copied folder to the version name e.g. MCS_v.vv.vv.vvv.

Zip the folder to the same name.

Create a release note in \\spekefs2012\Projects\Releases\MCS\Release Notes\.

Update the release log in \\spekefs2012\Projects\Releases\MCS\.

Release

On the customer machine, locate the customer MCS installation to be updated.

Delete any prior back-ups if appropriate.

Back-up the existing folder and zip it.

Copy the new release into the MCS installation folder.

Extract the contents of the new release zip over the existing folder.

Check and compare Web.config to Web.config.release - make any changes to the customer MCS installation version to reflect new keys added to the file.

Restart the system through IIS.

Inform the customer through email with the release note attached.