'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Can Windows Workflow Foundation Be Used in a .NET Core Application?
Question details
The user wants to know if Windows Workflow Foundation (WWF) can be used within a modern .NET Core application to securely call an HTTP Web API built with .NET Core.
- Product
- .NET Framework / .NET Core
- Device & OS
- not provided
- Scenario
- A developer is working on a sensitive-data project that requires integrating legacy workflow technology with a modern .NET Core Web API.
- Observed behavior
- Windows Workflow Foundation is a legacy .NET Framework technology and is not natively supported in modern .NET or .NET Core applications.
Verify the exact version of .NET Core or modern .NET your API targets, as bridging legacy .NET Framework applications with modern APIs requires cross-framework communication via HTTP rather than native integration.
Use an Intermediary Service or Alternative Workflow Engine
Because .NET Core does not natively support Windows Workflow Foundation, you must run the workflow on the .NET Framework and communicate with the .NET Core API over HTTP, or migrate to a modern workflow engine.
Windows Workflow Foundation is strictly tied to the older .NET Framework. To utilize it alongside a modern .NET Core API, you cannot host the workflow directly inside the .NET Core app. Instead, you need a microservices approach or a third-party workflow alternative.
Create a separate application or service strictly targeting the .NET Framework (e.g., .NET Framework 4.8) to host and execute your Windows Workflow Foundation logic.
Inside your .NET Framework workflow application, use standard HTTP clients (like HttpClient) to make secure, authenticated web requests to your sensitive-data .NET Core Web API.
If you prefer to keep everything in .NET Core, evaluate open-source workflow platforms that natively support modern .NET, such as Elsa Workflows or the community-driven CoreWF port.
Document Your Software Architecture Easily with WPS Office
When planning complex migrations from .NET Framework to .NET Core, drafting clear architectural diagrams, API specifications, and workflow logic is critical. WPS Office serves as a highly compatible, free alternative to Microsoft Office, providing developers with lightweight tools to create professional documentation.
- 1. Download the software: Navigate to the official WPS Office website and download the free installation package for your operating system.
- 2. Install the suite: Run the installer and follow the standard on-screen prompts to set up the lightweight office suite on your development machine.
- 3. Draft your workflow documentation: Open WPS Writer to seamlessly draft your .NET Core API documentation and insert flowcharts to visualize your legacy WWF integration.
Frequently Asked Questions
Is there any version of Windows Workflow Foundation for modern .NET?
Microsoft does not officially support Windows Workflow Foundation in modern .NET or .NET Core. However, the open-source community maintains a port called CoreWF that attempts to bring WWF runtime capabilities to .NET Core.
Can a .NET Framework application reference a .NET Core library directly?
Generally, no. Unless both projects explicitly target a mutually compatible version of .NET Standard, you cannot directly mix .NET Framework and .NET Core binaries. It is highly recommended to communicate between the two environments using HTTP APIs.
Where should developers seek help for specific .NET framework migration issues?
The best place to resolve specific .NET development and architectural problems is the official Microsoft Q&A platform (learn.microsoft.com/en-us/answers/), where Microsoft engineers and the developer community actively provide solutions.
