Recently I'm working on upgrading Tier 1 Dev box to 10.0.44. Multiple VMs (cloud hosted) are stuck in Step 27 related to DevTool installation. Previously I had incidents where the issue was due to D365 VS2022 extension not installed but I'm sure they are installed in this case.
After some deeper investigation and with some luck, I found out the reason was because of the version number of VS2022. The latest VS2022 version format has changed and have month date in it - "17.14.9 (july 2025)" instead of just "17.14.9". The breaks the PS script checking for existing Dev tools.
The solution is to update the PowerShell script to isolate the version number.
# Original string
$input = "17.14.9 (july 2025)"
# Use regex to extract the version number at the beginning
if ($input -match '^\d+(\.\d+)*') {
$versionString = $matches[0]
Write-Output "Extracted version string: $versionString"
} else {
Write-Error "No valid version number found in input."
}
Yes, you guessed it right, the above script block is generated by AI.
Well, thanks Microsoft for changing the version number format. 😑
This posting is provided "AS IS" with no warranties, and confers no rights.
Comments
Post a Comment