@carlfranklin Here's one for #SecurityThisWeek . Looks like a nightmare for all involved.
| 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
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!
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.
.NET📣Announcing .NET 8 RC2
https://devblogs.microsoft.com/dotnet/announcing-dotnet-8-rc2/
Scott GallowayRemember folks, this line in your Program.cs is EVIL...you might not notice until later but this freezes everyting in your WebApplicationBuilder as soon as it runs & creates singleton versions of any services you get using it.
Want to use a Bootstrap Logger...well now you can't.
await using var provider = services.BuildServiceProvider();
Want to use a Bootstrap Logger...well now you can't.
await using var provider = services.BuildServiceProvider();
Carl FranklinI'm very happy to announce the release of Polly v8 https://thepollyproject.azurewebsites.net/2023/09/28/polly-v8-officially-released/
Polly v8 officially released
After months of continuous development, Polly v8 is finally here! In our v8 announcement post, we discussed the background of the Polly project and what motivated us to completely redesign the library with a hyper-focus on performance. We were very fortunate to have top-notch developers from Microsoft do the bulk
On the one hand, I can see so many potential applications for this. On the other, I'm just thinking about how much more business critical logic is going to get lost in massive spreadsheets someone has just saved on their desktop.
https://www.theverge.com/2023/8/22/23841167/microsoft-excel-python-integration-support
New blog post on using embedded #aspnetcore appsettings files for when you don't want the loose files as part of your published #dotnet app:
Egil HansenThe new TimeProvider API in #dotnet now has a companion FakeTimeProvider from the .NET team.
I recommend using that instead of mocking TimeProvider, as it deals with many edge cases that will be tedious or impossible to set up using a mocking lib.
Here is the nuget package with the FakeTimeProvider: https://www.nuget.org/packages/Microsoft.Extensions.TimeProvider.Testing
