fix: Correct formatting in setup.ps1 output messages#506
fix: Correct formatting in setup.ps1 output messages#50677victor wants to merge 1 commit intomicrosoft:mainfrom
Conversation
Fixed the parse error in setup.ps1 by removing non-ASCII dash characters that were being misread by Windows PowerShell
|
👋 Thanks for contributing @77victor! We will review the pull request and get back to you soon. |
There was a problem hiding this comment.
Pull request overview
Updates setup.ps1 to avoid Windows PowerShell parse issues by replacing non-ASCII dash characters in user-facing console output.
Changes:
- Replace an em dash (—) with a standard hyphen (-) in the setup banner message.
- Replace an em dash (—) with a standard hyphen (-) in the prerequisites status message when
azis missing.
| $ErrorActionPreference = "Stop" | ||
|
|
||
| Write-Host "`n=== Generative AI for Beginners .NET — Automated Setup ===" -ForegroundColor Cyan | ||
| Write-Host "`n=== Generative AI for Beginners .NET - Automated Setup ===" -ForegroundColor Cyan |
There was a problem hiding this comment.
This change replaces em dashes in output strings, but setup.ps1 still contains a non-ASCII em dash in the header comment (currently on line 2: "setup.ps1 — Automated setup..."). If Windows PowerShell is misreading non-ASCII characters due to file encoding, the parse issue may persist until that remaining em dash is also replaced (or the file encoding is adjusted consistently).
There was a problem hiding this comment.
@copilot open a new pull request to apply changes based on this feedback
Fixed the parse error in setup.ps1 by removing non-ASCII dash characters that were being misread by Windows PowerShell