Empty Blazor WebAssembly Project Template

[cerasamson]

This creates an empty Blazor WebAssembly project template that contains minimal HTML/CSS formatting and no demo code or authentication options.

Screenshot of the current template:

Fixes #32832

[TanayParikh]

Looking great so far; left a few comments.

Also, we can remove the database:

src/ProjectTemplates/Web.ProjectTemplates/content/EmptyComponentsWebAssembly-CSharp/Server/app.db

[SteveSandersonMS]

If we're having the error styling, should we also have minimal styling for forms validation errors?

.valid.modified:not([type=checkbox]) {
    outline: 1px solid #26b050;
}

.invalid {
    outline: 1px solid red;
}

.validation-message {
    color: red;
}

[cerasamson]

I believe we wanted to eliminate as much CSS styling as possible, and the error styling was only kept as it was being used in \Client\wwwroot\index.html. The form validation styling was removed since it wasn't used in any of the existing code, but it can be added back to both templates.

[SteveSandersonMS]

Is the intent to support auth with this template? I don't personally mind either way about that, but if we are supporting auth, then I think there will also need to be an auth-enabled version of this file which uses AuthorizeRouteView. The non-empty template contains an example of this.

[TanayParikh]

Is the intent to support auth with this template?

Spoke with Dan regarding this earlier, and the conclusion was the empty template does not need to support auth.

[SteveSandersonMS]

@cerasamson This is looking really great! I'm definitely looking forward to having this template. No doubt customers will appreciate it a lot too.

Minor question: I noticed there's a file app.db. Is that meant to be there? I'm not sure what it's for.

And are we missing csproj files, or do they go somewhere else?

[SteveSandersonMS]

Here's a slightly controversial thought: we don't really need to have any "layout" in this template. We could just eliminate the MainLayout.razor file, and then developers would put whatever cross-page common UI they want in either index.html or App.razor. There isn't strictly any need for a 3rd choice of where to put common UI. Layouts as a feature are only relevant if you want different pages to have different layouts.

@danroth27 Interested to know if you have a view on this. In your experience, do people need layout components, and do you think they would struggle to add a "layout" component later if the project template didn't start with one?

Update Actually on further consideration, having this one extra very simple MainLayout.razor file doesn't really increase the conceptual complexity in any significant way, so I'd probably err on the side of keeping it in. The whole thing is still pretty elegant with or without it.

[cerasamson]

@SteveSandersonMS Thank you for the feedback! 😄

app.db was in the directory when I duplicated the original ComponentsWebAssembly-CSharp folder. I don't think it is being used in this template and will be removed.

The csproj files have not been added yet. They will be placed in the parent directory.

[TanayParikh]

Just confirming whether you've had a chance to test out these options on the CLI? Notably, the Hosted option is working appropriately (ie. creating empty blazor hosted vs empty blazor standalone).

[TanayParikh]

Looks great! 🚢 it!

[phenning]

LGTM now. Thanks!