Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

8.2K
Visualizações
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
14 Respostas
Responde à pergunta

0

The reason you are getting this error is because you do not have an exe file in your netcoreapp folder. Try and create a new project called HelloWorld1 and if VS19 doesn't create the files, you will need to uninstall and reinstall the application.

over 4 years ago · Santiago Trujillo Relatório

0

I tried multiple solutions for many days, but the only thing that worked for me was completely removing VS 2019 and then re-installing.

over 4 years ago · Santiago Trujillo Relatório

0

To solve your problem, you need to start a VS2019 as administrator and with this the project build will work normally.

enter image description here

Note: In my case the vs2019 is professional.

over 4 years ago · Santiago Trujillo Relatório

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 Relatório

0

Simple answer: Install .NET Core cross-platform development from the Visual Studio Installer in the Workloads tab. Totally working and tested here :)

over 4 years ago · Santiago Trujillo Relatório

0

For me, a wrong -path in the projectname.csproj.user was the problem. This drive me nuts! After deleting this file and rebuild the project, it finally worked.

over 4 years ago · Santiago Trujillo Relatório

0

I had a duplicate .AssemblyInfo.cs file within my project (one in the bin folder and one outside). This file is auto generated so what I did was removed both files, cleaned the project, ran a restore and then a rebuild. Fixed my issue.

over 4 years ago · Santiago Trujillo Relatório

0

I fixed it by right clicking the project, then "unload project", then right clicking again, then "reload project". Then running the project again and the error should be gone, at least for me

over 4 years ago · Santiago Trujillo Relatório

0

I have changed my solution name, it occurs this error. Then I changed all using packagename to correct one, then rebuild it. It works correctly.

over 4 years ago · Santiago Trujillo Relatório

0

  1. Check the output path of project (Project > right click Properties > Build > Output path) Output_Path
  2. Go to Build menu > Configuration Manager. Check the myMLApp has "Build" checked Build_projects
  3. Clean solution. Build solution.

source link

over 4 years ago · Santiago Trujillo Relatório

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 Relatório

0

So.... I’m using visual studio 2019 (version 16.10.2) on a windows 10. What fixed the issue for me were:

  1. Start a new project
  2. On the menu titled “Configure your new Project” I unchecked the option that says “place solution and project in the same directory”, then click next
  3. On the menu titled “Addition information”, I selected the current target framework which was “.Net5.0(Current)”, then click create.

Bamn!!! Fixed

over 4 years ago · Santiago Trujillo Relatório

0

I had this problem very recently with a fresh installation of visual studio 2022. The error occurred when I attempted to run a project with the 5.0 DotNet Framework specified instead of the default which was 6.0. I fixed the issue by modifying my installation with the installer and manually selecting DotNet 5.0 Framework to be installed because apparently it is not installed by default and only 6.0 is. The error message wasn't in the least bit helpful at telling me what I had to do. But after that everything runs without error.

over 4 years ago · Santiago Trujillo Relatório

0

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

over 4 years ago · Santiago Trujillo Relatório
Responde à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda