fenneh

param
(
  [string] $EnvironmentName,
	[string] $Version,
	[string] $ProjectName,
	[string] $OctopusApiKey,
	[string] $OctopusServerUrl,
	[string] $ReleaseNotes
)

fenneh

<Project DefaultTargets="CopyOutputs;DeployService" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">

  <!-- These settings control what the service's name, description etc appear in services.msc task panel. -->
	<PropertyGroup Label="ServiceMetaData">
		<ServiceName>ShinyNewService</ServiceName>
		<ServiceDisplayName>Shiny New Service</ServiceDisplayName>
		<ServiceDescription>A shiny new service, that changes the world for the greater good.</ServiceDescription>
	</PropertyGroup>

	<Choose>

fenneh

Set-StrictMode -Version Latest

$libPath = (Split-Path -Parent $MyInvocation.MyCommand.Definition)
Import-Module $libPath\SecurityLib.psm1

function New-WindowsService {
  param
	(
		[Parameter(Mandatory=$True,Position=0,HelpMessage="The name of the Windows Service")]
		[string]$serviceName,

fenneh

<#
.Synopsis
   Updates the Step Templates used on Deployment Processes to the latest versions
.DESCRIPTION
   Step templates can be updated from the library on Octopus, but that doesnt mean that the Deployment processes using that template will start using the latest version right away. Normally, the user would have to update the step template on each deployment process manually. This script takes care of that.
.EXAMPLE
   Update-StepTemplatesOnDeploymentProcesses -ActionTemplateID "ActionTemplates-3" -OctopusURI "http://localhost" -APIKey "API-RLMWLZBPMX5DRPLCRNZETFS4HA"
.EXAMPLE
   Update-StepTemplatesOnDeploymentProcesses -AllActionTemplates -OctopusURI "http://Octopusdeploy.MyCompany.com" -APIKey "API-TSET42BPMX5DRPLCRNZETFS4HA"
.LINK