Stephen Halter

We've joined Anthropic to launch a C# SDK for the Model Context Protocol! This open-source gem boosts #AI app dev with slick data integration, tailored for #dotNET. Serious power, flexibility, and totally extensible. Read the news and give it a tryout. 📖 msft.it/6012qqIim

Unfortunately, we’re going to need to delay the start of the API review streams for ASP.NET Core for now. We know a lot of you are excited about this (and so are we!), so we’re really sorry for the delay. We’re still committed to making this happen.

@kahbazi We'll be going over the issues listed at apireview.net/?g=aspnetcore starting with ones in the 10.0-preview1 milestone

@halter73 Is there a place that indicates which issues are being discussed in the meetings?

ASP.NET Core API reviews will be streaming live on @NETFoundation" target="_blank" rel="nofollow noopener">youtube.com/@NETFoundation starting this Thursday at 10 AM PST. See apireview.net/schedule for the full schedule. I hope to see many of you there!

The correct time is 3 PM PST this Thursday as shown on apireview.net/schedule. The Monday meetings will be at 10 AM to facilitate people in different time zones.

Proposal for a new scalable memory cache in .NET github.com/dotnet/extensi…

@anaximandus @davidfowl You can use the refresh endpoint to renew your access token without a 2fa code, but if you've enabled 2fa, you need to always pass the code for a new login.

Hello @davidfowl, I'm using the new IdentityEndpoints in an API which is supposed to provide token authentication to both a Web app and a Maui app. Do the endpoints support the "Remember this machine" feature for 2FA? Is there a sample to do that with Tokens?

@mahdertarik @captainsafia Starting in RC2 after we made the MapIdentityApi DTOs public, you can copy/paste the file containing MapIdentityApi from GitHub or using source link, rename it, and then customize it to your hearts content. github.com/dotnet/aspnetc…

@captainsafia The auth stuff on .NET 8 is great but would love to see the ability to turn on/off some of the endpoints (e.g. the register endpoint)

What "big" feature missing in minimal APIs keeps you up at night? 🤔 #dotnet

@Lowball42 @davidfowl Have you seen github.com/microsoft/coyo…?

Look at what you can do with a great debugger devblogs.microsoft.com/visualstudio/r… 👀 #visualstudio

@captainsafia and I are revealing the magic tomorrow. See you there!

Minimal APIs: The magic revealed @captainsafia @halter73 ignite.microsoft.com/en-US/sessions…

@buhakmeh These generic parameters are not required. This is the TBuilder and the key, and both can be inferred. We're updating the blogpost.

Looking at the #apsnetcore RC 1 notes and this looks… weird. I’m confused what the generics are about when it comes to rate limiting. Why “WebApplication” and why “string”?

@buhakmeh @RealSwimburger @davidfowl I doubt we're allowed to name and shame, but my initial reaction was definitely, "is this for real!? They can't just update their clients?" Let's just say it was above my pay grade. 🤣

@RealSwimburger @davidfowl This is interesting, I wish you named names. 😁

We spent the last 6 months moving Azure App Service from IIS and nginx to YARP + Kestrel to bring you gRPC and also take advantage of the massive performance improvements in .NET 6 🔥🔥🔥🔥 azure.github.io/AppService/202… #dotnet #aspnetcore #azure

@davidfowl Callback-based APIs are easy to use, but their major weakness is backpressure. You can do things like limit concurrent callbacks or tack on additional API, but having consumers manually dequeue work or read data when they're ready tends to be cleaner.

Spent some time debugging a couple of issues this week and all I can say is back pressure is *very* important. It must be built in at all layers of the system, all actors must comply and respect back pressure for it to work.

@Nick_Craver @marcgravell Did you talk to @Tratcher? What exactly broke in .NET 6? I thought we always left %2F escaped but clearly something changed. RawTarget is an escape hatch if the default unescaping of the PathString doesn't work. It is annoying we cannot just unescape everything.

@marcgravell THAT’S what was happening?!

Finally found the cause of a failure that I've been hunting for days; PathString has a breaking behaviour change in .NET 6 - fun fun fun; and the code I need to fix to repair this is going to be a devil to deploy whimper

@James_M_South @GeoffreyHuntley Depends on what kind of flexibility you need. It would be a shame if IDisposable was an abstract base class.

@GeoffreyHuntley It's all about this. 👇

Abstract class > Interface.

Have you tried the new Output Caching feature we shipped in #dotnet 7 preview 6? I am looking for any feedback before it's too late for changes.

@DamianEdwards @davidfowl Do you have an idea of what more strongly typed routes would look like?

@davidfowl Except routes *ducks*

The most natural thing to do when working with with weakly typed data in a strongly typed language is to turn it into something more strongly typed.

@jcarpenterdev @davidfowl If you don't want the "using Microsoft.AspNetCore.Mvc", you can use your own From* attributes that implement IFromBodyMetadata. You can look at the MVC parameter attributes for *Metadata interfaces to see what to implement.

@davidfowl That definitely what I want to see. Will .NET 7 final remove the dependency on Microsoft.AspNetCore.Mvc? I’m assuming that’s brought in by the From* attributes.

OK just got the latest build of .NET 7 preview hot off the CI machine. We now have route groups with support for filters and output caching. This is the brilliant work of @halter73, @captainsafia and @sebastienros #dotnet #aspnetcore

@buhakmeh @DamianEdwards @JetBrainsRider I bet it's not just collections and that you'll see the same thing for ValueTuple<object> or any other class with object properties. Minimal APIs unwraps returned Tasks, but recursively looking at the runtime type of every serialized object's sub elements would be too much.

@DamianEdwards @JetBrainsRider @halter73 It is kind of weird. I guess #aspnet could box all collections and force the "intuitive" behavior, but polymorphic results might be the exception to the norm.

Polymorphic serialization/deserialization in #dotnet 7 preview 5 is neat. #dotnet folks hate attributes 🤷‍♂️, so I wrote a #sourcegenerator that finds all derived types and creates the attributes for you in a partial class. @JetBrainsRider made it super easy. #aspnetcore #csharp