Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Could not attach to process with CustomPipeName: 'AzureFunctionsPSWorker'
See original GitHub issueI have a PowerShell Function App which I would like to build and test locally. Previously, I could run locally with no issue, but now this is no the case. When I type func host start or F5, I am prompted with the following error:
You must have the Azure Functions Core Tools installed to debug your local functions.
When I click install, I get the following error:
Could not attach to process with CustomPipeName: ‘AzureFunctionsPSWorker’
*** I have opened this issue in the vscode-azurefunctions repo as well. As I am not sure who can help me: https://github.com/microsoft/vscode-azurefunctions/issues/1744#issue-534941282
Issue Analytics
- State:
- Created 4 years ago
- Comments:28 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes I get this error in Powershell. I can meet at 1:00 which is my 3 pm.
I came across this in my search and I was having the issue described. I ran
func: host start --verboseI noticed the terminal log got hung on a step where it’s attempting to grab the latest Extensions for Azure Core tools (?). THen, I got the error described above.
That led me to remove the
"extensionBundle": {}block in thehosts.jsonfile of my project which ultimately resolved my issue.