CommunityToolkit / CommunityToolkit/Labs-Windows
Can't run in VS Code Locally
- Dominant language
- C#
- Stars
- 482
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
Looks like the revamp in #91 to make everything work in codespaces broke things from working in VS Code locally due to the use of `pwsh` in the `tasks.json` pre-launch step:
```
> Executing task: pwsh ./GenerateAllSolution.ps1 <
pwsh : The term 'pwsh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1
+ pwsh ./GenerateAllSolution.ps1
+ ~~~~
+ CategoryInfo : ObjectNotFound: (pwsh:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command pwsh ./GenerateAllSolution.ps1" terminated with exit code: 1.
Terminal will be reused by tasks, press any key to close it.
```
We need to figure out a way to make this work for both local and Codespace development on Windows/Linux, there must be something to handle this built into VS Code itself, right?
1. Clone main
2. Open up VS Code in root
3. Run and Debug 'All samples app'
4. See error.
On Win 10 latest.
Contributor guide
Assessment
This issue has not been assessed yet.