Custom .NET Framework Code Introduction for Standard Azure Logic Apps
Unveiling the .NET Framework Custom Code for Azure Logic Apps (Standard) with outstanding features like no-cliffs extensibility, local debugging in VS Code, and
Introducing .NET Framework Custom Code for Azure Logic Apps (Standard)
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 your workflow. In addition, this new capability provides the following benefits:
- 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.
Microsoft has announced a public preview of .NET Framework Custom Code for Azure Logic Apps (Standard). This feature allows users to invoke compiled .NET Framework code from a built-in action in their workflows. It provides several benefits including no-cliffs extensibility for low code offerings, no need for additional service plans, a local debug experience in VS Code, and support for BizTalk migration scenarios.
To use this feature, users need a working instance of VS Code, the Logic Apps (Standard) prerequisites, a Windows OS, and must support calling .NET Framework 4.7.2 assemblies.
A new logic app workspace template has been introduced for writing custom code. Users can author custom code and author workflows in two separate projects within this workspace.
Building and authoring custom code is done within the Functions project of the workspace. A .cs file contains a function created during the workspace setup, which demonstrates the capabilities of the custom code feature.
Once the custom code is authored, it needs to be compiled and placed in the lib/custom/net472 folder within the Logic App project. This is where workflows will search for custom code.
Debugging of the workflow and custom code is facilitated by Azurite and VS Code's Debug functionality. Users can set breakpoints in their code or workflow configuration.
Deployment of custom code follows the same method as workflow project deployment, with support for VS Code and CI/CD DevOps processes.
However, the Azure Portal currently doesn't support the authoring of custom code. Custom code extensibility is recommended for implementing custom business logic, custom parsing, data validation, message shaping, calculations, and simple data transformations.
As of now, support is prioritized for C# and .NET Framework due to BizTalk Migration needs, but the addition of other languages supported by Azure Functions is a possibility for the future.
Discover More About .NET Framework Custom Code for Azure Logic Apps (Standard)
.NET Framework Custom Code for Azure Logic Apps (Standard) is an innovative feature that enhances your workflow by allowing you to call compiled .NET Framework code from a built-in action. This not only offers developers greater flexibility and control but also eliminates the need for additional service plans. Additionally, it supports BizTalk migration scenarios, enabling easy transition of custom .NET Framework investments from on-premises to the cloud. With a local debug experience in VS Code, developers can seamlessly step through their workflows and code within a single debugging session, ultimately creating a more efficient and productive development environment.
Read the full article Introducing .NET Framework Custom Code for Azure Logic Apps (Standard)
Learn about Introducing .NET Framework Custom Code for Azure Logic Apps (Standard)
In order to use .NET Framework Custom Code for Azure Logic Apps (Standard), there are several prerequisites that must be met. These include having a working instance of VS Code with all the existing Logic Apps (Standard) prerequisites already installed, having the ability to deploy your custom code alongside your workflows, and having the ability to debug your workflows and code in the same debugging session. This new capability provides several benefits, including a no-cliffs extensibility capability to the low code offering, giving developers the flexibility and control they need to solve tough integration problems, no additional service plans being required, and the ability to lift and shift custom .NET Framework investments from on-premises to the cloud. With this feature, developers can call compiled .NET Framework code from a built-in action in their workflow.
More links on about Introducing .NET Framework Custom Code for Azure Logic Apps (Standard)
- A Step by Step Guide to Build Your First Azure Logic App ...
- Why Should You Use Azure Logic Apps Instead of Custom Code? Azure Logic Apps ... Azure Logic Apps is a framework that makes it easier to design complex workflows.
- Overview Of Azure Logic App And Creating Your First ...
- Nov 21, 2018 — NET workflow framework, custom code or third-party tools like, for SharePoint – Nintex. In Azure, we have one logic app service which we can ...
- Visual Studio Code - Developing Azure Logic Apps Course
- Visual Studio Code - Developing Azure Logic Apps course from Cloud Academy. Start learning today with our digital training solutions.
- Developing Logic App Standard Workflow Using Visual Studio ...
- Dec 16, 2022 — One of the feature is that we can develop logic app standard workflow locally using Visual studio code. In this post we will see how to setup ...
Keywords
.NET Framework, Azure Logic Apps, Extensibility, Service Plans, Debugging, VS Code, BizTalk Migration, Prerequisites