K
KentWeareMSFT
We are pleased to announce the General Availability (GA) of .NET Framework custom code for Azure Logic Apps (Standard). This capability allows customers to extend their low code solutions with the power of custom code. Once a developer has written and compiled their .NET Framework code, it can be called from a built-in action from within a workflow. In addition, this new capability provides the following benefits:
Developers can discover the custom code feature from within VS Code by clicking on the Azure 'A' and then clicking on the Logic Apps logo, followed by Create new logic app workspace.
You will be prompted for some additional information such as the name of your workspace, function name, namespace etc. We will then provision a sample C# project and workflow project so that you can easily get started. Below is an image of what you can expect. Within the workspace that is created you will see a Functions project that includes a sample function you can use to get started.
We will also provide a Logic App project that includes a sample workflow that includes the Call a local function in this logic app built-in action that allows you to call the compiled code.
Beyond all the capabilities we included in our public preview, we have also included support for local logging and support for Application Insights. This allows you to unify your traces across your workflow triggers and actions with your custom code. As a result, this additional logging support, we have updated the sample that gets provisioned in VS Code to include logging.
For a complete step-by-step walkthrough of how to use this new feature, please refer to our in-product documentation or watch the following YouTube video at the bottom of this page.
Custom code usage guidelines
Customers are encouraged to use .NET Framework custom code extensibility to complement their low code integration solutions that they build in Azure Logic Apps. In general, custom code extensibility can be used to:
Conversely, .NET Framework custom code extensibility is not a substitute for:
Please refer to the Azure Logic Apps limits and configuration reference for additional details.
Support for other languages?
We have priortized C# and .NET Framework support to help address BizTalk migration needs. We also recognize that there may be needs for other languages. We are actively working on building in support for .NET 6 and will share updates on this blog as they become available. Please add any additional languages that you would like to see support for in the comments.
Demo
To see a demo of this new capability, please check out the following video:
Continue reading...
- A no-cliffs extensibility capability to our low code offering giving developers the flexibility and control needed to solve the toughest integration problems.
- No additional service plans required, deploy your custom code alongside your workflows.
- A local debug experience, in VS Code, which allows you to step through your workflows and code in the same debugging session.
- Supports BizTalk migration scenarios by allowing customers to lift and shift their custom .NET Framework investments from on-premises to the cloud.
Developers can discover the custom code feature from within VS Code by clicking on the Azure 'A' and then clicking on the Logic Apps logo, followed by Create new logic app workspace.
You will be prompted for some additional information such as the name of your workspace, function name, namespace etc. We will then provision a sample C# project and workflow project so that you can easily get started. Below is an image of what you can expect. Within the workspace that is created you will see a Functions project that includes a sample function you can use to get started.
We will also provide a Logic App project that includes a sample workflow that includes the Call a local function in this logic app built-in action that allows you to call the compiled code.
Beyond all the capabilities we included in our public preview, we have also included support for local logging and support for Application Insights. This allows you to unify your traces across your workflow triggers and actions with your custom code. As a result, this additional logging support, we have updated the sample that gets provisioned in VS Code to include logging.
For a complete step-by-step walkthrough of how to use this new feature, please refer to our in-product documentation or watch the following YouTube video at the bottom of this page.
Custom code usage guidelines
Customers are encouraged to use .NET Framework custom code extensibility to complement their low code integration solutions that they build in Azure Logic Apps. In general, custom code extensibility can be used to:
- Implement custom business logic
- Custom parsing
- Data validation
- Message shaping
- Calculations
- Simple data transformations
Conversely, .NET Framework custom code extensibility is not a substitute for:
- BizTalk pipeline components that implement streaming
- Complex batching/debatching scenarios
- Code processes that exceed more than 10 minutes in duration.
- Large message data transformations.
Please refer to the Azure Logic Apps limits and configuration reference for additional details.
Support for other languages?
We have priortized C# and .NET Framework support to help address BizTalk migration needs. We also recognize that there may be needs for other languages. We are actively working on building in support for .NET 6 and will share updates on this blog as they become available. Please add any additional languages that you would like to see support for in the comments.
Demo
To see a demo of this new capability, please check out the following video:
Continue reading...