No job functions found if run "func start --no-build"

[doggy8088]

Here are the steps to reproduce the problem.

1. Check Azure Functions Core Tools version

   func --version

   3.0.3734

2. Use .NET Core 3.1.400 SDK

   dotnet new globaljson --sdk-version 3.1.400

3. Create function app

   func init MyFunc --worker-runtime dotnet
   cd MyFunc

4. Create a function

   func new --template "Http trigger" --name Funcion1

5. Starting my function app

   func start

   Here is the log (no problem):

   Azure Functions Core Tools
   Core Tools Version:       3.0.3734 Commit hash: 61192bb28820be76916f85209916152801483456  (32-bit)
   Function Runtime Version: 3.1.4.0
   
   [2021-09-10T15:17:20.590Z] Found G:\Projects\MyFunc\MyFunc.csproj. Using for user secrets file configuration.
   
   Functions:
   
           Funcion1: [GET,POST] http://localhost:7071/api/Funcion1
   
   For detailed output, run func with --verbose flag.

6. Starting my function app with --no-build option

   func start --no-build

   Here is the log (No job functions found):

   Azure Functions Core Tools
   Core Tools Version:       3.0.3734 Commit hash: 61192bb28820be76916f85209916152801483456  (32-bit)
   Function Runtime Version: 3.1.4.0
   
   [2021-09-10T15:18:27.514Z] Found G:\Projects\MyFunc\MyFunc.csproj. Using for user secrets file configuration.
   [2021-09-10T15:18:28.046Z] No job functions found. Try making your job classes and methods public. If you're using binding extensions (e.g. Azure Storage, ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. builder.AddAzureStorage(), builder.AddServiceBus(), builder.AddTimers(), etc.).
   For detailed output, run func with --verbose flag.

   I expected I can find all my functions with --no-build option because I already build my project.

[apsthisdev]

+1, Facing the same problem. The Blazor Static Web App + Azure Function + Playwright E2E tests setup requires the func start --no-build to start the func app without build.

Because of this issue I have to add an arbitrary delay in test execution for building the Azure Function and then continue e2e test. This increases the test execution time significantly.

[jonathanford]

Having the same issue when wanting to run the same function app locally multiple times with different environment variables.

[ameyasubhedarats]

It is impacting us as well. Task.Delay() to let the function app build first. E2E tests takes a long time to finish.

[cicorias]

what is going on with this? a freshly scaffolded project and getting this error message after second run.

why?

[zebleck]

same here

[Dona278]

How is possible after more than 2 years to have this issue? I tried to figure out the build-and-start process of a function but it is very complicated.

• Start a function from VS always build and run without issue. The output of the build is /bin/Debug/etc..
• Start a function with func start --port XXXX --verbose fail due to multiple project found... yes.. the inner autogenerated obj/Debug/net8.0/WorkerExtensions/WorkerExtensions.csproj is found
  • So delete the obj and re-run the command and the function builds and runs correctly, but the output folder is bin/output and no more bin/Debug/net8.0
  • Stop and re-run the command, same error of multiple csproj
  • So run the command with --no-build and tadan! No job to start.. and the searching is tried under bin/Debug..
• Same issue if we build first with visual studio and then try to start function with --no-build, the output folders mismatching

The only way to start a dotnet-isolated function locally with extension is run from VS, or manually delete the obj between executions.

[zebleck]

sorry, in my case I just forgot a correctly configured local.settings.json file.

[teyc]

• So run the command with --no-build and tadan! No job to start.. and the searching is tried under bin/Debug..
  • Same issue if we build first with visual studio and then try to start function with --no-build, the output folders mismatching

The only way to start a dotnet-isolated function locally with extension is run from VS, or manually delete the obj between executions.

Update your csproj file

    <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.17.2" />

and delete the obj and bin folder once, and the problem should be resolved, and you can run func start multiple times