Skip to content
Skills Library
Programming · Conversion & formats

logicapps-custom-code-net10-migration

/logicapps-custom-code-net10-migration

Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project/package configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.

Licence
MIT
Last repository change
07.11.2026

Assessment and security

98/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene13 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/migrate.py, tests/test_migrate.py

What it does and when to use it

Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project/package configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.

Original author description

Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project/package configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.

How it works

  1. Procedure
  2. Invariants
Original SKILL.md headings · 70 lines, 577 words
SKILL.md preview
---
name: logicapps-custom-code-net10-migration
description: 'Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project/package configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.'
license: MIT
---

# Logic Apps custom code .NET 10 migration

Read [the migration procedure](references/migration.md) before editing. Resolve bundled
files relative to this skill, not the target repository. Python 3.11+ is required only
for the helper; do not install dependencies or start services merely by activating this skill.

## Procedure

1. Establish the solution root, custom-code `.csproj`, and Logic Apps `host.json` root.
   Infer existing names/layout; ask only about ambiguous project selection or effects.
   Read repository instructions and affected configuration, including dirty changes,
   inherited build/package/SDK settings, workspace and tool paths. Do not inspect C#
   contents unless separately authorized to diagnose a build failure.
2. Run the bundled helper in its default dry-run mode:

   ```powershell
   python "<skill root>\scripts\migrate.py" --root "<solution root>"
   ```

   Use `--project "<csproj path>"` to select among multiple custom-code projects.
   The helper resolves `LogicAppFolderToPublish`; it does not require `Functions`
   or `LogicApps` folder names. Read all reported blockers/warnings. It prints no
   settings values and writes nothing in dry-run mode.
   Default edits cover framework/SDK/publication/runtime alignment, not reference
   dependency parity. Preserve absent Worker packages and existing debugger configuration.
   Use `--integrated-debug` only when coordinated launching is requested/needed.
3. For a requested migration, apply the reviewed plan with the same coordinates and
   `--apply`. Do not apply for a comparison/plan-only request. The helper guards changed
   files and rolls back its own completed writes on failure; it is not an atomic
   multi-file transaction or a persistent backup. Preserve unrelated user edits.
4. If the helper refuses central/conditional/imported configuration, newer unreviewed
   SDK targets, or an unfamiliar debugger/layout, do not bypass the guard. Read the
   owning configuration, resolve scope with the user when shared projects are affected,
   and make targeted agent edits using repository tools. Never claim universal helper
   coverage. Repeat the dry run to check idempotency for supported layouts.
5. Validate with the repository's build/analyzers and approved package source. Use the
   exact SDK selected by VS Code, not just PATH. Verify assembly/dependency publication
   and generated local-function metadata. Obtain permission for trigger/connector
   effects before host startup or workflow execution. Follow the installed Logic Apps
   runtime skill/procedure when available; otherwise perform ownership-aware VS Code
   launch and verify actual execution, not just debugger attachment.
   If the SDK's directory scan fails on a clean build, rerun the helper dry run/apply
   with `--ensure-output-directory`, then repeat the failed build. Do not introduce
   the guard as a universal framework requirement. Resolve genuine missing-dependency
   errors individually; do not add Worker/HTTP/telemetry packages just to match a sample.
6. Report changed configuration, dry-run/apply/tests, and separate states:
   configuration migrated, build verified, local-function execution verified.
   State blockers plainly. Always report the later deployment prerequisite:
   Azure app settings must carry `LOGIC_APPS_CUSTOMCODE_DOTNETVERSION=net10.0` and
   `FUNCTIONS_INPROC_NET8_ENABLED=1`. Deployment through the Logic Apps extension
   in VS Code copies these settings; pipelines must explicitly include them.
   A local settings file alone does not configure Azure. Do not deploy, change
   Azure app settings, or assert cloud/production support.

## Invariants

- Only upgrade the custom-code library; preserve host .NET 8 configuration.
- Preserve names, workflows, connections, authentication, storage, unrelated dependencies,
  workspace/task conventions, comments and secret exclusions.
- Do not add sample-only HTTP, telemetry or framework references.
- Do not introduce `Program.cs` or an executable worker host. Library `Main()` is
  not automatically executed; source preservation is intent, not verified API compatibility.
- No C# rewrites, SDK installation, restore, host start, Azure mutation or persistent
  secret backups inside the configuration helper.
- Do not silently downgrade packages, rewrite shared package management, suppress
  restore/build errors, copy .NET 10 DLLs to `net472`, or manufacture passing checks.

Installation and test commands are in [README.md](README.md).
Files in this package (6)
  • LICENSE 1 KB
  • README.md 6 KB
  • SKILL.md 5 KB
  • references/migration.md 10 KB
  • scripts/migrate.py 29 KB
  • tests/test_migrate.py 23 KB

Versions

RepositoryScoreLicence
This page · wsilveiranz/custom-code-net1098MIT
github/awesome-copilot98MIT

Database snapshot: 13.11.2026 · package version 0f647ed3ad3a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100azure-logic-apps-standard-cli
    Create, inspect, validate, test, run, debug, package, and deploy Azure Logic Apps Standard projects using the Azure CLI logicapp extension. Use for Standard workflow authoring, optional workspaces, connector discovery, identity-based connections, local runtimes, native workflow…
  • 85azure-functions
    Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models. Use when: azure function, azure functions, durable functions,…
  • 100azure-functions-update
    Use only when the user explicitly asks to use or resume azure-functions-update by name. Migrate Azure Functions programming models and configuration through an approved scenario. Current scenario: C# in-process to .NET isolated worker; more scenarios are planned.…
  • 100azure-functions-tests
    Runs Azure Functions locally using Azure Functions Core Tools v4 (`func start`), Azurite storage emulation, and framework-native unit tests for handler code (.NET isolated worker model, Node.js v4, Python v2). Covers HTTP, queue, and timer trigger testing, admin-endpoint…
  • 100azure-functions
    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns. USE FOR: working on Azure Functions in .NET; migrating from the in-process model to the isolated worker model; adding Durable…
  • 95azure-functions
    Expert knowledge for Azure Functions development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when wiring Functions to HTTP/storage/queues, using bindings, VNet/private…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.