Skill
.NET Aspire
Build, upgrade, and operate .NET Aspire application hosts with current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, and Azure deployment patterns for…
dotnet skills install aspire
Azure Functions for .NET
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.
Trigger On
- working on Azure Functions in .NET
- migrating from the in-process model to the isolated worker model
- adding Durable Functions, bindings, or host configuration
Workflow
- Use isolated worker model for all new work:
- In-process model reaches end of support on November 10, 2026 - Runtime v1.x ends support on September 14, 2026 - Target .NET 8+ for longest support window
- Detect current project shape:
- Target framework and runtime version - Worker model (isolated vs in-process) - Binding packages and host configuration
- Use standard .NET patterns in isolated model:
- Normal dependency injection - Middleware pipeline - IOptions<T> for configuration - ILogger<T> for logging
- For Durable Functions:
- Validate orchestration determinism constraints - Handle replay behavior correctly - Use typed activity patterns
- Verify both local and deployment behavior.
Deliver
- correct Functions project setup for the isolated worker model
- clear binding and host configuration
- middleware for cross-cutting concerns
- Durable Functions with proper orchestration patterns
- migration-safe guidance when upgrading execution models
Validate
- execution model guidance is consistent (isolated only for new work)
- orchestrator code is deterministic
- bindings and host settings match the target runtime
- large payloads are externalized to blob storage
- retry policies are configured for transient failures
- local and deployment behavior are both verified