Dashes in a hosted Blazor WebAssembly project name break OIDC security

Describe the bug

I have created multiple Blazor WASM apps with ASP.NET hosting and Individual Authentication from the base template, but none of them run upon initial creation. I always get the following error:

It doesn’t happen with Standalone Blazor WASM apps with Individual Authentication and it doesn’t happen with Blazor WASM apps with ASP.NET Hosting and NO authentication. Just when both are used.

The Client project is created fine and exists in the solution. I don’t know why the Server project can’t find it.

To Reproduce

1. Open Visual Studio 2019 and select Create New Project.
2. Select Blazor WebAssembly App project Template.
3. Enter a name for the project.
4. Check the ASP.Net Hosted option box.
5. Select Individual Authentication for the Authentication type.
6. Create Project.
7. Wait for Solution to load then run Server project.
8. Browser opens and shows a partial Blazor page then the Exception is hit.

Exceptions (if any)

System.InvalidOperationException: Client 'Blazor-WASM-Hosted-Auth-Demo.Client not found

Further technical details

• ASP.NET Core version 5.0
• • Visual Studio 2019 16.11.0
• Output of dotnet --info

.NET SDK (reflecting any global.json):
 Version:   5.0.400
 Commit:    d61950f9bf

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19042
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\5.0.400\

Host (useful for support):
  Version: 5.0.9
  Commit:  208e377a53

.NET SDKs installed:
  3.1.412 [C:\Program Files\dotnet\sdk]
  5.0.302 [C:\Program Files\dotnet\sdk]
  5.0.400 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 3.1.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.18 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.18 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.18 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.8 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

cc: @guardrex

[pranavkm]

Will this issue be addressed with a framework update such that dashes will be permitted at some point in the future

We don’t plan on changing the behavior since the workaround is trivial. A bot usually closes resolved issues after it gives the users time to respond.

[Cmohan]

I tried both BlazorWasmHostedAuthDemo and Blazor_Wasm_Hosted_Auth_Demo as project names and those both worked fine. It definitely doesn’t like the dashes then.