Add ability to update publish url and install url

- Added the ability to pass in either the publish url or install
url and it will update the csproj file. If no parameter is provided
they will remain the same

- Switched around some right side null comparisons to left ones
due to warning encountered from VS Code and after doing a little research.
Found this article https://rencore.com/blog/powershell-null-comparison/

- Added tests for the publish url and install parameters

- Added test for using both the Version parameter and the BuildId
parameter. Passing in 1.0.0.0 as the Version and along with a BuildId
the version will keep the hardcoded major/minor(1.0) and update the
build/revision(0.0) with the autogenerated id

Author: Brett Groff

Set-ProjectFilesClickOnceVersion.ps1

@@ -29,6 +29,12 @@
 	If this switch is provided, the ClickOnce MinimumRequiredVersion will be updated to match the new Version.
 	Setting the MinimumRequiredVersion property forces the ClickOnce application to update automatically without prompting the user.
 
+.PARAMETER PublishUrl
+	If this string is provided, it will update the PublishUrl. If it is not provided, the PublishUrl will remain what it is currently. This should be a UNC type file path (e.g. \\servername\foldername)
+
+.PARAMETER InstallUrl
+	If this string is provided, it will update the InstallUrl. If it is not provided the InstallUrl will remain what it is currently. This should be a URL type path (e.g. http://servername/foldername)
+
 .EXAMPLE
 	Update a project file's ClickOnce version to the specified version.
 	
@@ -54,6 +60,17 @@
 	
 	& .\Set-ProjectFilesClickOnceVersion.ps1 -ProjectFilePath "C:\SomeProject.csproj" -Version '1.2.3' -IncrementProjectFilesRevision -UpdateMinimumRequiredVersionToCurrentVersion
 	
+.EXAMPLE
+	Update a project file's ClickOnce version using both Version and a unique, auto-incrementing integer, such as a build system's Build ID. This will keep the major and minor versions you specify but update the build and revision (e.g. 1.0.1.5745)
+
+	& .\Set-ProjectFilesClickOnceVersion.ps1 -ProjectFilePath "C:\SomeProject.csproj" -Version 1.0.0.0 -BuildSystemBuildId 123456
+
+.EXAMPLE
+	Update a project file's ClickOnce version and its install and publish url values.
+
+	& .\Set-ProjectFilesClickOnceVersion.ps1 -ProjectFilePath "C:\SomeProject.csproj" -Version 1.0.1.9 -PublishUrl "\\servername\foldername" -InstallUrl "http://servername/foldername"
+
+
 .LINK
 	Project Home: https://github.com/deadlydog/Set-ProjectFilesClickOnceVersion
 	
@@ -81,7 +98,13 @@ Param
 	[switch]$IncrementProjectFilesRevision = $false,
 
 	[Parameter(Mandatory=$false,HelpMessage="When the switch is provided, the ClickOnce Minimum Required Version will be updated to this new version.")]
-	[switch]$UpdateMinimumRequiredVersionToCurrentVersion = $false
+	[switch]$UpdateMinimumRequiredVersionToCurrentVersion = $false,
+
+	[Parameter(Mandatory = $false, HelpMessage="The Publish URL to update to.")]
+	[string]$PublishUrl = '',
+
+	[Parameter(Mandatory = $false, HelpMessage="The Install URL to update to.")]
+	[string]$InstallUrl = ''
 )
 
 # If we can't find the project file path to update, exit with an error.
@@ -92,16 +115,16 @@ if (!(Test-Path $ProjectFilePath -PathType Leaf))
 }
 
 # If there are no changes to make, just exit.
-if ([string]::IsNullOrEmpty($Version) -and $BuildSystemsBuildId -lt 0 -and !$IncrementProjectFilesRevision -and !$UpdateMinimumRequiredVersionToCurrentVersion)
+if ([string]::IsNullOrEmpty($Version) -and $BuildSystemsBuildId -lt 0 -and !$IncrementProjectFilesRevision -and !$UpdateMinimumRequiredVersionToCurrentVersion -and !$InstallUrl -and !$PublishUrl)
 {
-	Write-Warning "None of the following parameters were provided, so nothing will be changed: Version, BuildSystemsBuildId, IncrementProjectFilesRevision, UpdateMinimumRequiredVersionToCurrentVersion"
+	Write-Warning "None of the following parameters were provided, so nothing will be changed: Version, BuildSystemsBuildId, IncrementProjectFilesRevision, UpdateMinimumRequiredVersionToCurrentVersion, InstallUrl and PublishUrl"
 	return
 }
 
 function Get-XmlNamespaceManager([xml]$XmlDocument, [string]$NamespaceURI = "")
 {
     # If a Namespace URI was not given, use the Xml document's default namespace.
-	if ([string]::IsNullOrEmpty($NamespaceURI)) { $NamespaceURI = $XmlDocument.DocumentElement.NamespaceURI }	
+	if ([string]::IsNullOrEmpty($NamespaceURI)) { $NamespaceURI = $XmlDocument.DocumentElement.NamespaceURI }
 
 	# In order for SelectSingleNode() to actually work, we need to use the fully qualified node path along with an Xml Namespace Manager, so set them up.
 	[System.Xml.XmlNamespaceManager]$xmlNsManager = New-Object System.Xml.XmlNamespaceManager($XmlDocument.NameTable)
@@ -179,7 +202,7 @@ function Set-XmlElementsTextValue([xml]$XmlDocument, [string]$ElementPath, [stri
 
 function Set-XmlNodesElementTextValue([xml]$xml, $node, $elementName, $textValue)
 {
-	if ($node.($elementName) -eq $null)
+	if ($null -eq $node.($elementName))
 	{
 		$element = $xml.CreateElement($elementName, $xml.DocumentElement.NamespaceURI)		
 		$textNode = $xml.CreateTextNode($textValue)
@@ -210,7 +233,7 @@ $propertyGroups = Get-XmlNodes -XmlDocument $xml -NodePath 'Project.PropertyGrou
 }
 
 # If no ClickOnce deployment settings were found throw an error.
-if ($clickOncePropertyGroups -eq $null -or $clickOncePropertyGroups.Count -eq 0)
+if ($null -eq $clickOncePropertyGroups -or $clickOncePropertyGroups.Count -eq 0)
 {
 	throw "'$ProjectFilePath' does not appear to have any ClickOnce deployment settings in it. You must publish the project at least once to create the ClickOnce deployment settings."
 }
@@ -223,6 +246,24 @@ foreach ($clickOncePropertyGroup in $clickOncePropertyGroups)
 	$numberOfClickOncePropertyGroupsProcessed++
 	Write-Verbose "Processing ClickOnce property group $numberOfClickOncePropertyGroupsProcessed of $numberOfClickOncePropertyGroups in file '$ProjectFilePath'."
 
+	# If publish url is provided, update it
+	$publishUrl = $PublishUrl
+	if (![string]::IsNullOrEmpty($publishUrl))
+	{
+		Write-Verbose "Publish Url is '$publishUrl'"
+		Write-Output "Updating PublishUrl to be '$publishUrl'"
+		Set-XmlNodesElementTextValue -xml $xml -node $clickOncePropertyGroup -elementName 'PublishUrl' -textValue "$publishUrl"
+	}
+
+	# If install url is provided, update it
+	$installUrl = $InstallUrl
+	if (![string]::IsNullOrEmpty($installUrl))
+	{
+		Write-Verbose "Install Url is '$installUrl'"
+		Write-Output "Updating Install Url to be '$installUrl'"
+		Set-XmlNodesElementTextValue -xml $xml -node $clickOncePropertyGroup -elementName 'InstallUrl' -textValue "$installUrl"
+	}
+
 	# If the Version to use was not provided, get it from the project file.
 	$appVersion = $Version
 	if ([string]::IsNullOrEmpty($appVersion))
@@ -261,7 +302,7 @@ foreach ($clickOncePropertyGroup in $clickOncePropertyGroups)
 	{
 		# If the Revision is missing from the file, or not in a valid format, throw an error.
 		$applicationRevisionString = $clickOncePropertyGroup.ApplicationRevision
-		if ($applicationRevisionString -eq $null)
+		if ($null -eq $applicationRevisionString)
 		{
 			throw "Could not find the <ApplicationRevision> element in the project file '$ProjectFilePath'."
 		}		
@@ -304,4 +345,4 @@ foreach ($clickOncePropertyGroup in $clickOncePropertyGroups)
 }
 
 # Save the changes.
-$xml.Save($ProjectFilePath)
+$xml.Save($ProjectFilePath)

Tests/RunTests.ps1

@@ -60,3 +60,17 @@ if ($output -eq '1.2.1.57922') { Write-Host "Passed" } else { throw "Test $testN
 Write-Host ("{0}. Use version number parameter and update minimum required version..." -f ++$testNumber)
 $output = RunScriptWithParameters "-Version '5.6.7.8' -UpdateMinimumRequiredVersionToCurrentVersion"
 if ($output.Contains("Updating minimum required version to be '5.6.7.8'.")) { Write-Host "Passed" } else { throw "Test $testNumber failed. Output was '$output'." }
+
+Write-Host ("{0}. Use major/minor of version number parameter and Build Id parameter...." -f ++$testNumber)
+$output = RunScriptWithParameters "-Version '1.1.0.0' -BuildSystemsBuildId 123456"
+if ($output -eq '1.1.1.57921') { Write-Host "Passed" } else { throw "Test $testNumber failed. Output was '$output'." }
+
+Write-Host ("{0}. Use version and publish url parameter...." -f ++$testNumber)
+$output = RunScriptWithParameters "-Version '1.0.5.9' -PublishUrl 'http://testserver/folder'"
+# Multiple output statements are objects in an array in the order they are outputted
+if ($output[0].Contains('http://testserver/folder') -AND $output[1].Contains('1.0.5.9')) { Write-Host "Passed" } else { throw "Test $testNumber failed. Output was '$output'." }
+
+Write-Host ("{0}. Use BuildId parameter, publish url parameter and install url parameter...." -f ++$testNumber)
+$output = RunScriptWithParameters "-BuildSystemsBuildId 123456 -PublishUrl 'http://testserver/folder' -InstallUrl '\\fileshare\folder'"
+# Multiple output statements are objects in an array in the order they are outputted
+if ($output[0].Contains('http://testserver/folder') -AND $output[1].Contains('\\fileshare\folder') -AND $output[2].Contains('1.0.1.57921')) { Write-Host "Passed" } else { throw "Test $testNumber failed. Output was '$output'." }

Tests/TestFiles/TestProject.csproj

@@ -24,6 +24,7 @@
     <UpdatePeriodically>false</UpdatePeriodically>
     <UpdateRequired>true</UpdateRequired>
     <MapFileExtensions>true</MapFileExtensions>
+    <InstallUrl>\\publish\app</InstallUrl>
     <MinimumRequiredVersion>1.0.0.1</MinimumRequiredVersion>
     <ApplicationRevision>1</ApplicationRevision>
     <ApplicationVersion>1.0.0.%2a</ApplicationVersion>
@@ -134,4 +135,4 @@
   <Target Name="AfterBuild">
   </Target>
   -->
-</Project>
+</Project>