With "Do not use top-level statements" checked, in Blazor WebAssembly App/ Blazor Server App/gRPC, the namespace is "Company.WebApplication1" rather than the solution name.

[Andy-Win]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

In Blazor WebAssembly App/ Blazor Server App/gRPC, the namespace is "Company.WebApplication1" rather than the solution name.

Expected Behavior

The namespace should be same as the solution name.

Steps To Reproduce

In latest Dev17.2 GA(Include latest 6.0.300 SDK), Create .NET 6.0 ~ Blazor Server App/Blazor WebAssembly App/gRPC project with checking "Do not use top-level statements" checkbox..
After project created, open Program.cs file, the namespace is "Company.WebApplication1", rather than the solution name.

Exceptions (if any)

No response

.NET Version

6.0.300

Anything else?

No response

[javiercn]

@Andy-Win thanks for contacting us.

@DamianEdwards can you take a look?

[DamianEdwards]

I'll look at adding a test that ensures the template's configured sourceName does not appear in the template output content so this doesn't happen again.

[mkArtakMSFT]

@DamianEdwards I think this should be closed already, shouldn't it?

[DamianEdwards]

Yes, thanks!