logicapps-custom-code-net10-migration
/logicapps-custom-code-net10-migration
Migruje projekty custom code w Azure Logic Apps Standard z .NET 8 do .NET 10: pakiety, konfigurację i publikację.
- Autor
- wsilveiranz ↗
- Repozytorium
- custom-code-net10 ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 07.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 6
- Skrypty
- 2
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/migrate.py, tests/test_migrate.py
Co robi i kiedy
Migruje projekty custom code w Azure Logic Apps Standard z .NET 8 do .NET 10: pakiety, konfigurację i publikację.
Oryginalny opis (EN)
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.
Jak działa
- Procedure
- Invariants
Podgląd SKILL.md
--- 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).
Pliki w paczce (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
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · wsilveiranz/custom-code-net10 | 98 | MIT |
| github/awesome-copilot | 98 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 0f647ed3ad3a (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100azure-logic-apps-standard-cli
Tworzy, sprawdza, testuje, uruchamia, debuguje, pakuje i wdraża projekty Azure Logic Apps Standard przez rozszerzenie logicapp w Azure CLI. - 85azure-functions
Opisuje wzorce pracy z Azure Functions: model isolated worker, orkiestracje Durable Functions, optymalizację zimnego startu i wzorce produkcyjne dla .NET, Pythona i Node.js. - 100azure-functions-update
Migruje model programowania Azure Functions z C# in-process na izolowany worker .NET w zatwierdzonym scenariuszu, uruchamiany tylko na wyraźne wywołanie po nazwie. - 100azure-functions-tests
Testuje Azure Functions lokalnie z Core Tools v4, emulacją Azurite i testami jednostkowymi handlerów (.NET, Node.js, Python): triggery HTTP, kolejki i timera oraz bindingi z local.settings.json. - 100azure-functions
Pomaga budować, przeglądać i migrować Azure Functions w .NET: model wykonania, izolowany worker, bindingi, DI, wzorce Durable Functions i migracja z modelu in-process. - 95azure-functions
Dostarcza wiedzę ekspercką o Azure Functions: łączenie z HTTP, storage i kolejkami, bindingi, VNet i prywatne endpointy, tożsamość zarządzana oraz wdrożenia CI/CD.