I thought I would take up the challenge of getting @enhance_dev#WASM working with #aspnetcore with the ability to SSR web components directly into the request pipeline.
Only a few years ago, there was a considerable effort in #dotnet to make interoperability with #nodejs a thing... now it seems like all those projects are gone or woefully behind. Bummer :(
Every few months, I come back to rewriting a #todo app in #aspnetcore, sometimes it's with Blazor, sometimes it's Razor Pages, and this time with #Htmx (although I may have already done HTMX 😅)
I got some quality-of-life improvement issues entered to help make #JetBrainsRider better, too. So that's a win!
@jonstj Woah, a lot of questions. I’ll answer them one at a time. 1. “Do you consider Razor Page with HTMX the best production-ready tech stack for HTMX-powered SSR web?” I think Razor Pages and MVC are great options, and they give you the most control over the HTTP response (which is essential to get the most out of HTMX). My HTMX.NET library is designed to work with #aspnetcore in helpful ways that I haven't seen in other ecosystems. (1/3)
An #aspnetcore#Blazor user asked for help this week regarding a blog post I had written, which made me revisit a demo I did and think about @alexzeitler HX-Trigger post.
After some exploration, I managed to uncover a solution for Blazor Components. This solution allows you to set headers, enabling the triggering of HTMX requests upon response.
If you're curious about #HTMX and #aspnetcore and how they can work together, check out this sample using Hx-Trigger to trigger other elements to update from a single request.
This is nice if you have global shared state like a shopping cart, score, etc.
I’ll repeat it. #aspnetcore should cater harder to the web designer community with static site generation, razor build steps for prerendering JS/Web components, and more JS build-tool integration.
It's a missed opportunity for #dotnet as these folks use their talents elsewhere.
One of my favorite #aspnetcore features in the latest #JetBrainsRider release is resolving addTagHelper and removeTagHelper assemblies for developers.
You wouldn't believe how often I've seen folks get these wrong (even in popular OSS projects). The default behavior is to ignore unresolved registrations, so folks are left debugging this in frustration. WELL NO MORE!
I wonder if y’all can help me out—I’m trying to collect a list of web development communities (not related to any one specific tool or framework), can you reply with your favorites?
(if you don’t have a favorite I will also accept communities you’re familiar with 😅)
So, it turns out, ASP.NET Core applications without Open Telemetry still send a traceparent header, with the tracing flag off. It also turns out that an ASP.NET Core application that does use OTEL will not send traces if they receive a traceparent header with the tracing flag off. And it also turns out, that the documentation on how to change this behaviour, by using the OTEL_TRACES_SAMPLER environment variable, is incorrect. This variable is not used yet. Fun. #OpenTelemetry#DotNet#ASPNETCore
#JetBrainsRider found a referencing bug with tag helpers in OrchardCore that's been there for at least four 4 years in the project. It shows there's still room to improve the dev experience regarding #aspnetcore.
I wish the #dotnet localization story would get a modern facelift. Instead, we deal with 20-year-old XML files, numeric placeholders, and object arrays.
@b4ux1t3 It’s partly the file format and the IStringLocalizer interface that’s janky. The issue is that IStringLocalizer is threaded through a lot of #aspnetcore that needs to be redone by the #dotnet team.
I like where this guy was going, where there was syntax that could be post-processed, but the model changed so much that it was abandoned (like many projects).