Fix Azure Container Apps deployment failure with uppercase resource names

[Copilot]

Problem

Adding project references with uppercase names (e.g., "WebFrontEnd") would work fine locally but cause deployment failures when publishing to Azure Container Apps:

Error: Invalid ContainerApp name 'WebFrontEnd'. A name must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character and cannot have '--'. The length must not be more than 32 characters.

Root Cause

While the Container App's Name property was being set to lowercase, the Bicep resource identifier was still using the original uppercase name. Azure Container Apps require lowercase names, but the generated Bicep template contained uppercase identifiers, causing deployment failures.

Solution

Updated ContainerAppContext.cs to ensure both the Bicep resource identifier and container names are lowercase:

1. Line 59: Fixed Bicep identifier creation to use lowercase name:

   var containerAppResource = new ContainerApp(Infrastructure.NormalizeBicepIdentifier(resource.Name.ToLowerInvariant()))

2. Line 104: Fixed container name to use lowercase:

   containerAppContainer.Name = resource.Name.ToLowerInvariant();

Testing

• Added comprehensive test ContainerAppWithUppercaseName_ShouldUseLowercaseInManifest
• Verified that uppercase "WebFrontEnd" correctly becomes lowercase "webfrontend" in generated Bicep
• All 46 Azure Container Apps tests pass with no regressions

Developer Experience

• Developers can continue using any casing they prefer (e.g., "WebFrontEnd", "MyApi")
• Names are automatically converted to comply with Azure Container Apps requirements
• No breaking changes or additional warnings needed
• Deployments now succeed reliably

This approach is consistent with existing Azure naming patterns throughout the codebase where automatic lowercase conversion is commonly used.

Fixes #4505.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[davidfowl]

@copilot the container app name is being lowercased multiple times, we want to do it once. Also the host name calculated in ProcessEndpoints also uses the resource name (which maps to the container app name). Let's have a single property that represents the normalized container app name that will be used as the EndpointMapping host name and the name of the container app.

Also remove setting the container app name multiple times.

[Copilot]

@copilot the container app name is being lowercased multiple times, we want to do it once. Also the host name calculated in ProcessEndpoints also uses the resource name (which maps to the container ap...

I've refactored the code to address your feedback. The changes include:

1. Added a single NormalizedContainerAppName property that computes resource.Name.ToLowerInvariant() once
2. Replaced all multiple calls to ToLowerInvariant() with this property
3. Updated endpoint mappings to use the normalized name for host names
4. Ensured consistent usage throughout the container app creation process

The normalized container app name is now used consistently for both the Bicep resource identifier and endpoint mapping host names as requested. Commit: 4cb15cf