- Scale the project back to a single Blazor WebAssembly reference template. See readme.
- Temporarily remove
.vscode
items.
- Bump to .NET 7 & Tailwind CSS 3.2
- Content rehash: put only the most applicable content in
index.html
/Index.razor
and link to the slightly-more-significantly rehashedtailblazor.dev
for more info. - Remove the
Hosted
WIP project. (Still need to decide what the template structure will look like long-term.)
- Latest tailwindcss (3.1.4)
- Update content text to reflect minor version change.
- Remove
tailblazormaui
WIP project. npm audit -fix
andnpm update
anddotnet outdated -u
things and stuff
npm audit fix
for minimist vulnerability
Misc:
- C# 10 more things where possible
- Latest tailwindcss (3.0.23)
- Update
tailwindcss.targets
files as described here
(Projects in WIP
have not been updated.)
Functional:
- Add (most) VSCode launch configs back in.
- Make
.vscode
folder andwatch
scripts optional:vsc
andps1
boolean parameters for CLI, default totrue
. VS integration TBD. - Trim down DarkSwitch code. JS code came from a multi-themed project hence the unneeded switch; dark/light theme initialization moved from component's backing code to JS.
- Add WIP Blazor Wasm Hosted project. Not a template (yet?) as Hot Reload doesn't work well for Hosted project types.
- Add "Blazor Pages" projects: Razor Pages + Tailwind 3 + Razor Component integration. Both single project and an addition to the MultiProject. Use
_Layout.cshtml
rather than BlazorMainLayout
. Hot Reload TBD: might end up in "WIP" folder with Hosted. - Remove
typography
dependency. - Update
DarkSwitch
to use explicit values; remove outer padding. - Add
'!**/{bin,obj,node_modules}/**'
content filter totailwind.config.js
Content:
- Split single page in two:
- Landing page. Meant to use project type's "native" page:
cshtml
for Razor Pages this release,xaml
for MAUI upcoming, ... - Usage info. Routable (Razor) Component.
- Extract "app" CSS to share in
index.html
/_Layout.cshtml
- Add filename footers to pages to visualize layouts.
Misc:
- Improve site loader a bit: Spinny radial gradient but not face; add text.
- Remove
<AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>
from thecsproj
files and docs: MAUI needs this.
Change tailblazor-full
solution, namespaces, and generated CSS from "TailBlazor" to "TailBlazorFull". When using the template, Index.razor
's informative text would be mangled to include things like "What is Project1?".
Initial NuGet package release with single-project BlazorWasm and BlazorServer templates, and a Multi-Project (Solution) template with BlazorWasm and BlazorServer projects sharing a Razor Class Library.