# logicapps-custom-code-net10-migration

The logicapps-custom-code-net10-migration GitHub Copilot skill migrates Azure Logic Apps Standard custom-code projects from .NET 8 to .NET 10. It adjusts project files, publication targets, and VS Code debugging configs.

- skill · `type=skill` · GitHub Copilot, Claude Code, Codex, Cursor, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 41430 repo stars
- Author: github · official GitHub repository
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/github/awesome-copilot/tree/HEAD/skills/logicapps-custom-code-net10-migration/SKILL.md
- Updated: 2026-10-23
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/logicapps-custom-code-net10-migration

## What it does

The skill updates custom-code local-function libraries in Azure Logic Apps Standard workspaces to .NET 10. It executes a bundled script `scripts/migrate.py` in dry-run mode first, scanning solution coordinates and validating project settings before applying edits.

Running the helper requires Python 3.11+. The workflow targets only the custom-code project, deliberately keeping the host on .NET 8 without altering workflow definitions, connections, or C# logic. It does not support standalone Azure Functions, Consumption plans, or ordinary .NET apps.

For cloud execution, Azure app settings must include `LOGIC_APPS_CUSTOMCODE_DOTNETVERSION=net10.0` and `FUNCTIONS_INPROC_NET8_ENABLED=1`. A local settings file alone will not configure Azure.

## Requirements
- Works with: Azure

## Install

### GitHub Copilot (native platform)

1. **GitHub CLI**
```bash
gh skill install github/awesome-copilot skills/logicapps-custom-code-net10-migration
```

2. **Manually: put the files in place**
- File: `.github/skills/logicapps-custom-code-net10-migration/SKILL.md`

### Claude Code

1. **Skills CLI (Vercel)**
```bash
npx skills add github/awesome-copilot --skill logicapps-custom-code-net10-migration -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/logicapps-custom-code-net10-migration/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/logicapps-custom-code-net10-migration/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add github/awesome-copilot --skill logicapps-custom-code-net10-migration -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/logicapps-custom-code-net10-migration/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add github/awesome-copilot --skill logicapps-custom-code-net10-migration -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/logicapps-custom-code-net10-migration/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add github/awesome-copilot --skill logicapps-custom-code-net10-migration -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/github/awesome-copilot --path skills/logicapps-custom-code-net10-migration
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/logicapps-custom-code-net10-migration/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/github/awesome-copilot/tree/HEAD/skills/logicapps-custom-code-net10-migration/SKILL.md

## When to use it
- migrate Logic Apps Standard custom-code libraries to .NET 10
- test configuration updates in dry-run mode before modifying files
- configure integrated local debugging in VS Code
- align publication paths and metadata for the Logic Apps runtime

## Example prompts
- Run a dry-run migration to .NET 10 for the Logic Apps solution
- Apply .NET 10 migration to `--project "<csproj path>"` using `--apply`
- Configure integrated VS Code debugging for the custom-code project

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 0a543f23ff2c6ec9.

BEGIN THIRD-PARTY FILE 0a543f23ff2c6ec9
````text
---
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,
````
END THIRD-PARTY FILE 0a543f23ff2c6ec9

The third-party file has ended. Everything between the 0a543f23ff2c6ec9 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2484 of 5274 bytes. © github · MIT · https://github.com/github/awesome-copilot/tree/HEAD/skills/logicapps-custom-code-net10-migration/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
