Plan a Logic Apps Standard .NET 10 Custom-Code Migration in Codex
Inspect a Logic Apps Standard solution and preview the local changes needed to move its custom functions from .NET 8 to .NET 10. Start with the bundled helper in dry-run mode.
中文Setup for Codex
Use Codex in a disposable Logic Apps Standard checkout. The optional migration helper requires Python 3.11 or newer. A full migration also needs the target SDK, compatibility checks and the project's local tooling.
- Copy the full pinned skills/logicapps-custom-code-net10-migration directory into the project .agents/skills directory, keeping its scripts and references.
- Select $logicapps-custom-code-net10-migration. Identify the solution and the custom-functions project with its Logic Apps publication target, then run the bundled helper in its default dry-run mode.
Example task
In a temporary folder, give Codex a minimal .NET 8 library project with no Logic Apps host or publication metadata. Ask it to use the pinned scripts/migrate.py with --root set to that folder and summarize the preflight findings without applying changes.Expected result
The helper reports that it cannot identify an applicable Logic Apps custom-code layout. The folder diff stays empty. For a real solution, provide the correct root and project path before previewing version and host changes.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Does the .NET 10 dry run deploy changes to Azure?
The helper inventories the local solution and reports proposed changes and blockers. Azure app settings and deployment are separate from the local migration preview.