home.social

#minimalapis — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #minimalapis, aggregated by home.social.

  1. Next week the RGVDevs Dot Net user group for the #RGV goes live! Our first meeting is a deep dive into building an #AI Brand Engine with #MinimalAPIs and the #MicrosoftAgentFramework Excited to show the community what modern #DotNet is capable of!

    Details: qr.pageinit.net/apimaf

  2. Next week the RGVDevs Dot Net user group for the #RGV goes live! Our first meeting is a deep dive into building an #AI Brand Engine with #MinimalAPIs and the #MicrosoftAgentFramework Excited to show the community what modern #DotNet is capable of!

    Details: qr.pageinit.net/apimaf

  3. Next week the RGVDevs Dot Net user group for the #RGV goes live! Our first meeting is a deep dive into building an #AI Brand Engine with #MinimalAPIs and the #MicrosoftAgentFramework Excited to show the community what modern #DotNet is capable of!

    Details: qr.pageinit.net/apimaf

  4. Next week the RGVDevs Dot Net user group for the #RGV goes live! Our first meeting is a deep dive into building an #AI Brand Engine with #MinimalAPIs and the #MicrosoftAgentFramework Excited to show the community what modern #DotNet is capable of!

    Details: qr.pageinit.net/apimaf

  5. Next week the RGVDevs Dot Net user group for the #RGV goes live! Our first meeting is a deep dive into building an #AI Brand Engine with #MinimalAPIs and the #MicrosoftAgentFramework Excited to show the community what modern #DotNet is capable of!

    Details: qr.pageinit.net/apimaf

  6. New post from my blog...

    In case you missed it earlier...

    FastEndpoints vs ASP.NET Minimal APIs in 2026
    barretblake.dev/posts/developm

  7. fast-endpoints.com/ - for devs, Fast Endpoints is an alternative to .

  8. Kind of sad that the linked issue, about being able to tailor a nice 400 response with actionable information for the API client, doesn't seem to even come close to be a priority.

    Does nobody care about providing information about what went wrong when handling an API request? I'd think this should be a must from the get go, but given its complete absence from the framework and lack of folks asking for it, maybe I'm the minority here.

    #DotNet #CSharp #MinimalApis

    github.com/dotnet/aspnetcore/i

  9. Kind of sad that the linked issue, about being able to tailor a nice 400 response with actionable information for the API client, doesn't seem to even come close to be a priority.

    Does nobody care about providing information about what went wrong when handling an API request? I'd think this should be a must from the get go, but given its complete absence from the framework and lack of folks asking for it, maybe I'm the minority here.

    #DotNet #CSharp #MinimalApis

    github.com/dotnet/aspnetcore/i

  10. Kind of sad that the linked issue, about being able to tailor a nice 400 response with actionable information for the API client, doesn't seem to even come close to be a priority.

    Does nobody care about providing information about what went wrong when handling an API request? I'd think this should be a must from the get go, but given its complete absence from the framework and lack of folks asking for it, maybe I'm the minority here.

    #DotNet #CSharp #MinimalApis

    github.com/dotnet/aspnetcore/i

  11. Kind of sad that the linked issue, about being able to tailor a nice 400 response with actionable information for the API client, doesn't seem to even come close to be a priority.

    Does nobody care about providing information about what went wrong when handling an API request? I'd think this should be a must from the get go, but given its complete absence from the framework and lack of folks asking for it, maybe I'm the minority here.

    #DotNet #CSharp #MinimalApis

    github.com/dotnet/aspnetcore/i

  12. Kind of sad that the linked issue, about being able to tailor a nice 400 response with actionable information for the API client, doesn't seem to even come close to be a priority.

    Does nobody care about providing information about what went wrong when handling an API request? I'd think this should be a must from the get go, but given its complete absence from the framework and lack of folks asking for it, maybe I'm the minority here.

    #DotNet #CSharp #MinimalApis

    github.com/dotnet/aspnetcore/i