Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

439
Views
Visual Studio - Debug Executable Specified in the Debug Profile does not Exist

I am trying to run a simple HelloWorld C# .NET Core Console Application and I get this error. Being fairly new, I couldn't resolve it upon trying certain things mentioned in another answer. Please guide me on how to resolve it.

The error I get is:

The debug executable [PATH] specified in the [Project Name] debug profile does not exist.

Visual Studio Screenshot

over 4 years ago · Santiago Trujillo
3 answers
Answer question

0

For me, all I needed to do was modify the Project Properties (right click the project in the Solution Explorer --> Project Properties), then under the Application tab, select an appropriate Target Framework. It was unset for me by default.

over 4 years ago · Santiago Trujillo Report

0

Copy the "cli" folder and rename it to "cli_x64". This works for me.

over 4 years ago · Santiago Trujillo Report

0

Solution for Azure Functions

  1. Make sure you have azure-functions-core-tools installed.
  2. Open up your project's properties, right-click project root | properties | Debug You should see this: enter image description here
  3. Set the Launch to Executable
  4. Set the Executable to the path of your azure-functions-core-tools executable - in AppData\Roaming\npm\node_modules\azure-functions-core-tools\bin\func.exe
over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!