Why Won't Azure Logic Apps Standard Open in VS Code Designer Mode?

Below are some troubleshooting steps that might help resolve the "[No job functions found]" issue when opening Logic Apps Standard in designer mode:

1. Ensure Public Accessibility and Proper Attributes
   Double-check that your workflow classes and methods are public. For a method to be recognized as a job (or function), it needs to be declared public and, depending on your project, decorated with the proper attribute (for example, [Function("Name")] in a Functions project). If a function isn’t public, it won’t be discovered.

2. Verify Binding Extension Registrations
   If you use binding extensions (e.g., Azure Storage, Service Bus, Timers), make sure you call the relevant registration methods in your startup code. In an isolated-process model, this might look like:

   CSHARPCopied
   var host = new HostBuilder()
       .ConfigureFunctionsWorkerDefaults(builder =>
       {
           builder.AddAzureStorage();
           builder.AddServiceBus();
           builder.AddTimers();
           // Add other extensions as needed
       })
       .Build();
   
   host.Run();

   Confirm that these registrations match those required by the bindings used in your workflows.

3. Configuration Files Check
   Since you mentioned following the GitHub steps (modifying host.json, local.settings.json, and adding workflow-designtime.csproj), ensure there are no errors or typos in these files. Even a small misconfiguration can prevent the runtime from locating your functions. For example, verify that:

   • Your host.json contains settings appropriate for your extension registrations.
   • local.settings.json includes all necessary keys and values.
   • The workflow-designtime.csproj correctly references your source files and targets the appropriate .NET SDK and runtime.

4. Build and Dependencies
   Make sure that your project is building correctly before attempting to open it in designer mode. Sometimes the designer won’t detect functions if the project hasn’t been completely compiled or if there are dependency issues.

   A clean rebuild of the project can also help, so try deleting the bin and obj folders and building again.

5. Review the Startup Code
   In the case of using an isolated worker model (common with Logic Apps Standard), verify that your startup code is correctly interconnected with your function definitions. Confirm that there is no conflict between the runtime version your project is targeting and the configuration set in the design-time files.

6. Check for Known Issues/Updates
   Sometimes the extension versions or tooling may have known issues. Check for any available updates to the Logic Apps or Azure Functions extensions in VS Code. Also, take a look at the issue on GitHub again to see if any new workarounds or patches have been suggested.

If after going through these steps you still encounter the issue, it may be helpful to enable more detailed logging to gain further insight into what the runtime is examining during startup. This logging might reveal if certain assemblies are failing to load or if configuration values aren’t being picked up as expected.

By verifying these items, you should have a clearer idea of whether the problem is due to the function/method visibility, improper registration of extensions, or misconfiguration in your project files.