aspire-project-endpoint-profiles

Synchronize .NET Aspire endpoint advertisements with project launch profile configurations.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill aspire-project-endpoint-profiles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-project-endpoint-profiles
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.claude/skills/aspire-project-endpoint-profiles
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill aspire-project-endpoint-profiles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves configuration drift between .NET Aspire resource advertisements and the actual launch profiles of executable projects, preventing dashboard URL mismatches and downstream connection errors.

Core Features & Use Cases

  • Endpoint Synchronization: Ensures Aspire-advertised localhost URLs match the Kestrel bindings defined in project launchSettings.json.
  • Configuration Consistency: Provides patterns for deriving downstream service URLs from a single source of truth to avoid hardcoded port conflicts.
  • Use Case: When a developer adds a new microservice to the stack, this skill guides the configuration of launch profiles to ensure the Aspire dashboard correctly detects and proxies the service without manual port adjustments.

Quick Start

Use the aspire-project-endpoint-profiles skill to audit the launchSettings.json files in the current directory and verify they match the advertised endpoints in the AppHost.

Frequently Asked Questions about aspire-project-endpoint-profiles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my .NET Aspire dashboard show mismatched localhost URLs for my microservices?

Mismatched localhost URLs occur due to configuration drift between .NET Aspire resource advertisements and actual Kestrel bindings in launchSettings.json. Synchronizing endpoint profiles ensures the Aspire dashboard correctly detects and proxies services without manual port adjustments.

How do I align .NET Aspire AppHost endpoints with project launchSettings.json?

Align .NET Aspire AppHost endpoints with launchSettings.json by auditing project configurations to verify advertised endpoints match Kestrel listeners. Deriving downstream service URLs from a single source of truth eliminates hardcoded port conflicts.

What is the best way to prevent hardcoded port conflicts in .NET Aspire local development?

Prevent hardcoded port conflicts in .NET Aspire by deriving service URLs from a unified configuration origin. Validating that AppHost and project launch profiles share a single source ensures reliable service-to-service communication.

Can I use .NET Aspire endpoint synchronization without manually adjusting Kestrel port bindings?

Yes, .NET Aspire endpoint synchronization eliminates manual Kestrel port adjustments by ensuring Aspire-advertised localhost URLs match the bindings defined in launchSettings.json, providing consistent local development environments.

How do I fix downstream connection errors when adding a new microservice to .NET Aspire?

Fix downstream connection errors in .NET Aspire by configuring launch profiles to ensure advertised endpoints match Kestrel listeners. This validates that AppHost and project configurations share a unified origin for service discovery.

When should I audit launch profiles to prevent .NET Aspire configuration drift?

Audit launch profiles to prevent .NET Aspire configuration drift whenever adding a new microservice to the stack. Verifying that launchSettings.json matches advertised AppHost endpoints prevents dashboard URL mismatches and downstream connection errors.