Docs should be as much of a source of truth as the code itself, but they also *need* the human element to be effective! @github Agentic Workflows have helped us find a balance between automated and handcrafted content that never falls out of sync, no matter how many features we ship. Blog by our very own @davidpine7 💫
Docs shouldn’t trail the code.
The Aspire team used GitHub Agentic Workflows to turn merged features into cross-repo docs PRs, with scoped permissions and SME review.
Results: 82/82 merged, with a 44.8-hour median time to merge. ✅
https://t.co/P4jplftmFx
Announcing Aspire 13.2! Overhauled to be agent friendly, CLI first, revamped VS code extension and more!
https://t.co/sBwygcEJNU
#aspiredev@aspiredotdev
.NET Aspire ❌
Aspire ✅🤌🏼
we're officially rebranding - starting with our shiny new website, https://t.co/y0pWH3gibp 💫
join us for a special edition #AspiriFriday to wrap up the week and celebrate with the team! see you there 🎃
@tannerelectric I’m sure you don’t get this as often as you deserve, but thanks a lot for all your hard work and getting us back online and keeping us updated along the way!
Mark your calendars & join me with @davidfowl & @maddymontaquila for a #dotnet Aspire 9 RC.1 AMA next Tuesday, Oct 15 at 10AM PDT!
https://t.co/xUYAeY2IWr
.NET Aspire 9.0 RC1 is out!
⏯️ Start/stop/restart
📢 Resource commands
⏰ WaitFor
🧑⚕️ Health checks
🌏 Browser telemetry
📌 Persistent containers
And much more. Full release notes:
https://t.co/Msh1qglQOR
🌐 Excited about .NET and cloud development? 🚀 Don't miss out! Dive into the latest insights at the .NET Aspire Developers Day. Watch the live stream now: https://t.co/PnH7OnyZGt 📺💻 #DotNet#CloudDevelopment#DevelopersDay#aspire
Today, we announced the general availability of .NET Aspire - an opinionated and flexible stack to build cloud native applications. So proud of the work the team has done and can't wait to see what developers build with the same. #dotnet#MSBuild
https://t.co/0nfzwCc1EC
@TeBeClone @davidfowl Regarding the update issue you are hitting, seems like some Mono toolchain packages were in the middle of publishing when you ran into this. Things are published now, can you try again?
@TeBeClone @davidfowl workloads can also target an older SDK band than the one you are using (in this case, Mono is targeting 8.0.100 which is compatible with your 8.0.200 SDK) (2/2)