Are we all ready to watch #dotnetconf in 24 hours?
(So we can skip over each mention of "Copilot" or "AI" and get to the real stuff)
11.11.2025 15:29
👍 1
🔁 0
💬 0
📌 0
Are we all ready to watch #dotnetconf in 24 hours?
(So we can skip over each mention of "Copilot" or "AI" and get to the real stuff)
Well you're just doing everything I wrote about after the preview - it's a happy time 🤩 The closer Aspire gets to being production-ready by default, the better it is for everyone!
This gets us one step closer to writing less Bicep - along with the ACA configuration and reduction of magic (azd and key vault)!
Finally, we have some more app security in .NET Aspire learn.microsoft.com/en-us/dotnet...
What IDE are you using? This is treated correctly by Rider at least, and I'm assuming Roslyn in general.
Is this a thing we’re meant to be able to deal with? 😫
Now all the SPA folk can stop whining there’s no official hash based router!
The only thing for the left to moan about is it being file system based 🧐
A SQL migration description in JSON with a tag of "minor carnage".
Yep, this seems about right for a SQL Migration name. Thanks @drizzle.team
It has got quieter the past week or so.
It's nice of the aliens to respect our port/starboard navigational lights though.
Just so I've got this straight, in the USA they believe that planes are alien drones now?
Today we added a whole new module. svelte/reactivity/window exports a variety of reactive values like innerWidth, innerHeight, scrollX, scrollY and so on. Like the MediaQuery introduced on day 5 and Spring and Tween from day 6, these are class instances with a reactive current property that you can use in your template and in deriveds/effects. Behind the scenes, Svelte handles all the event listener stuff.
Another banger from Advent of @svelte.dev, whilst this was possible before having it built in to the framework and avoiding in-app bindings for these things is a big win.
This is just proving that small, incremental changes can make a huge difference to UX.
You saw it here first, cos it's not live yet - but Svelte 5.10.0 containing the change is 👍
When Svelte emits a warning or error (whether at build time, when the compiler is running, or when the app is running on the server or in the browser) it will now be accompanied by a link to the corresponding entry in the documentation containing a description (which is omitted from production builds, to save bytes) and — in some cases, with more to come — more details on why it happened and what you can do to fix it.
Advent of @svelte.dev Day 9 now gives us proper links to errors in the svelte documentation.
Demo: svelte.dev/playground/8...
PSA for MacOS users that use PiP for videos:
Hold ⌘ when dragging to put it anywhere rather than the annoying snapping locations!
You can't open it in GitHub Desktop anymore. Progress!
Chaos Engineering by default
It always starts with a goodie
over-engineering a solution to a problem, as is tradition
It really depends on the workload you’re going to put through it. We can run certain things comfortably in a 0.5 core Azure container, and I doubt they’re very powerful cores to begin with.
Very well if you ever wanted to try 😃 Of course not for anything too complex, but basic APIs work quite well in a small memory (and CPU) environment.
We took a client project from 6 to 9 last week. No issues at all (though it was quite surprising!).
They work surprisingly well for AOT Web APIs too, especially in .NET 9 👍
Function bindings You can also use bind:property={get, set}, where get and set are functions, allowing you to perform validation and transformation: <input bind:value={ () => value, (v) => value = v.toLowerCase()} /> In the case of readonly bindings like dimension bindings, the get value should be null: <div bind:clientWidth={null, redraw} bind:clientHeight={null, redraw} >...</div> Function bindings are available in Svelte 5.9.0 and newer.
Advent of @svelte.dev Day 8 is a good one!
Game show where _anything_ could happen?
.NET. Only .NET.
Just a mini @tiptap.dev JSON to HTML renderer in C# because I couldn't find one on the internet
github.com/rudiv/Tippyt...
💯
Awesome, it looks great 😃
Typically this is some mismatched version of .NET vs NuGet packages. For example if you are running .NET 8, but have a package (generally System.Something included from another package) that's a lower version, you could run in to this issue. Check that first as there could be other reasons.
There's quite a few of us on here, what's up?
bsky.app/starter-pack...
bsky.app/starter-pack...
blueskystarterpack.com/starter-pack...