@philvessey Don't leave out the lovely surprise when you change nothing and they break anyway because of some change in the build host.
| My Blog | https://codemindinterface.com |
| GitHub | https://github.com/bowencode |
John Bowen
- 17 Followers
- 33 Following
- 76 Posts
Software Engineer, Consultant, Solliance partner, .NET, and Identity
@shanselman I don't know if it's the same way in FL but the one in CA is often that way at the end of the night too, with the different experience of everything being lit up.
@rockylhotka The Existing Investments point I think is probably the biggest one, especially given that Blazor has mostly been an all or nothing proposition. Since at least the start of core it's been relatively simple to mix most of those listed techs into an existing app that uses the others. That can get adoption up a lot faster than needing to start new apps from scratch.
@carlfranklin Here's one for #SecurityThisWeek . Looks like a nightmare for all involved.
@shanselman How else can you explain having made almost 1000 episodes covering nearly that many different topics?
Tim 
Have to say this to counteract my recent bitching. We're ~6 weeks into building a #dotnet 8 #MAUI and #blazor hybrid LOB client application with a #aspnetcore Web Api/Blazor server, and it's all coming together really nicely! Despite the prerelease challenges, it's amazing how much code reuse one can do across multiple client and web platforms.
New blog post on detecting how components are being rendered in #dotnet 8 #blazor and displaying it in real time on the page to help reason about what the code is doing and debug the weird issues that are sure to come up with mixed mode apps. #dotnet8
https://codemindinterface.com/2023/10/blazor-rendermode-visuals/
Visualizing .NET 8 Blazor Component Render Locations
The New World of .NET 8 Blazor originally allowed a choice of either Server or WASM (browser client) rendering, but this was an exclusive choice which applied across an entire application. Many things behave differently depending on where they are running, but there was no ambiguity within a single app. Now that .NET 8 is beginning to support the “Blazor United” concept of mixed rendering modes within an application, including adding a third option to statically pre-render in the style of Razor Pages, different parts of your application may render in different places, and can even switch modes on the fly at runtime!
@TimPurdum I thought that was the goal too. I don't remember exactly but thought one of the early preview releases said that WebAssembly was separate project for now but would change later. The current state does still feel like a hosted WASM app.
Took my frustrations and investigations into #dotnet 8 #Blazor changes and channeled it into a blog post. Hopefully this will help others understand the differences between Blazor Server, Blazor #WebAssembly, and the new Blazor Web App.
https://timpurdum.dev/2023/10/14/comparing-blazor-net-7-8.html
Comparing Blazor Project Structure in .NET 7 and 8
.NET 8, which is currently a preview Release Candidate (RC2) and will be released fully next month, brings about vast changes in the structure of Asp.NET Core Blazor projects. The goal behind these structural changes is to support, from a single project, the ability to render pages and components as static html, server-connected interactive, or WebAssembly-based client interactive. Previously, when developing a project, one would have to choose between Blazor Server and Blazor WebAssembly, and static rendering was not an option.
@carnage4life And it's from the period ending in 2013, before Nadella was even CEO! He must be cursing Ballmer today.