Blog Post

Azure Integration Services Blog
6 MIN READ

Announcement: Introducing .NET Framework Custom Code for Azure Logic Apps (Standard) - Preview

KentWeareMSFT's avatar
KentWeareMSFT
Icon for Microsoft rankMicrosoft
Jun 22, 2023
We are pleased to announce the public preview of .NET Framework Custom Code for Azure Logic Apps (Standard). This capability allows you to call compiled .NET Framework code from a built-in action in ...
Updated Jun 22, 2023
Version 1.0
logic apps
prasadagv's avatar
prasadagv
Copper Contributor
Nov 20, 2024

Hi KentWeareMSFT ,

Everything works fine when using a single .cs file with one function. However, I wanted to add additional functions and tried the following approaches, but the new function doesn't appear in the dropdown of the Local Function action in Logic Apps (I also restarted VS Code). Did build the function after making changes.  Could you please advise?

1. Added a new function with a different name in the Function attribute and implemented a Run method (resulting in two Run methods in the same .cs file). This caused a compilation error:
System.Reflection.AmbiguousMatchException: Ambiguous match found for ... Run...

2. Added a new function with a different name in the Function attribute, using the same new name for the method. The code compiled successfully, but the function still doesn't show up in the Local Function dropdown in Logic Apps.

3. Created a new .cs file and added a new function with a different name in the Function attribute and a Run method. While the code compiled successfully, the function still doesn't appear in the Local Function dropdown in Logic Apps.