Powershell script for generating a version number and inserting it into the csproj

SetCsProjVersion.ps1

$csprojPath = $args[0] # path to the file i.e. 'C:\Users\ben\Code\csproj powershell\MySmallLibrary.csproj'
$newVersion = $args[1] # the build version, from VSTS build i.e. "1.1.20170323.1"

Write-Host "Starting process of generating new version number for the csproj"

$splitNumber = $newVersion.Split(".")
if( $splitNumber.Count -eq 4 )
{
	$majorNumber = $splitNumber[0]
	$minorNumber = $splitNumber[1]
	$revisionNumber = $splitNumber[3]
	
	# I need to keep my build number under the 65K int limit, hence this hack of a method
	$myBuildNumber = (Get-Date).Year + ((Get-Date).Month * 31) + (Get-Date).Day
	$myBuildNumber = $majorNumber + "." + $minorNumber + "." + $myBuildNumber + "." + $revisionNumber

	$filePath = $csprojPath
	$xml=New-Object XML
	$xml.Load($filePath)
	$versionNode = $xml.Project.PropertyGroup.Version
	if ($versionNode -eq $null) {
		# If you have a new project and have not changed the version number the Version tag may not exist
		$versionNode = $xml.CreateElement("Version")
		$xml.Project.PropertyGroup.AppendChild($versionNode)
		Write-Host "Version XML tag added to the csproj"
	}
	$xml.Project.PropertyGroup.Version = $myBuildNumber
	$xml.Save($filePath)

	Write-Host "Updated csproj "$csprojPath" and set to version "$myBuildNumber
}
else
{
	Write-Host "ERROR: Something was wrong with the build number"
}

I came across your script over here but ran into an issue in the 1.* PowerShell Script Task (I am running it Inline). It kept tossing an error that PropertyGroup did not contain a Property named Version. This threw me because it has no problem getting the value from $xml.Project.PropertyGroup.Version when it exists.

I ended up using XPath to get the node and set the InnerText:

$xml=[xml](get-content $src)
# just to ensure it actually exists. 
if ($xml.Project.PropertyGroup.Version -eq $null) { $xml.Project.PropertyGroup.AppendChild($xml.ImportNode(([xml]"<Version/>").DocumentElement,$true)) }
$xml.SelectNodes("/Project/PropertyGroup/Version")[0].InnerText = [version]($args[2])
$xml.Save($src)

I really, really hate powershell.. Struggled forever with 'property does not exist' errors, so I punted and said "if it doesn't exist, perhaps it shouldn't (legacy cs proj format for one)..

function Set-CSProj-Version{
Param(
[parameter(Mandatory=$true)] [String] $filePath,
[parameter(Mandatory=$true)] [String] $newVersion
)

$xml=New-Object XML
$xml.Load($filePath)

if ($xml.Project.PropertyGroup.Properties.name -match "Version")
{
$xml.Project.PropertyGroup.Version = $newVersion
$xml.Save($filePath)
}
}

I updated the above script to create the version tag if it doesn't exist. Realized that if you have a new project and haven't changed the version number in the properties > package tab, the version tag won't exist in the XML doc. VS assumes that, since it doesn't exist, it's 1.0.0. I've also written a new blog post to show how to support .NET Core 2.0 and .NET Standard 2.0

Thanks for posting this script, it saved me the time of writing it from scratch.

Changes not reflected on build process if script triggered from Pre-build event. MSBuild didn't notice *.csproj file changes on the fly. How to resolve that?

$xml.Project.PropertyGroup might require index[0] to avoid set error because there might be several nodes PropertyGroup in your csproj

I use:
$xml.Project.PropertyGroup[0].FileVersion = $newVersion

on my project

God bless you ;)