Reference to {ASSEMBLY NAME}.styles.css as the generated css file seems to be incorrect or incomplete

[ocdsoft]

Description

I added a <PackageId></PackageId> to the project file and altered the name slightly from the {AssemblyName}. The output of the generated css file changed to the packageID name {PackageID}.styles.css while the output of project {AssemblyName}.dll remained the same.

net6.0

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/components/css-isolation?view=aspnetcore-8.0&source=docs

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/css-isolation.md

Document ID

39d464d9-aca6-34fa-7e52-5fde2e393ba7

Article author

@guardrex

[github-actions]

😎 March! The gateway to spring! 🌞

A green dinosaur 🦖 will be along shortly to assist. Stand-by ........

[guardrex]

Hello @ocdsoft ... That's not uncommon when supplying a PackageId for various assembly-named things. I think the best way to handle this is to make a note on an existing issue that deals with component library authorship that we're going to be working on. The new article can cover your request. I'll make a cross-link on that issue now to your issue here, and we can close this one.

[jbennink]

[EDIT by guardrex to add code fencing. Note @jbennink that tags don't display without it.]

I ran into this and it was very hard to find what was wrong. I also had a project that included a <PackageId> which changes from the <AssemblyName> which was also included. I don't understand what @guardrex was trying to say, but the Docs at aspnetcore/blazor/components/css-isolation.md clearly state {ASSEMBLY NAME} which is obviously not completly correct since using a <PackageId> and <AssemblyName> tag mean that blaozr used the PackgeId name as the css file and NOT the Assemblyname.