khalidabuhakmeh, 4 months ago to dotnet

Today, I’ll discuss #dotnet and #odata with @cwoodruff on the #JetBrains webinar.

Did you know OData was first dreamt up in 2007 and is still used today in services like #Azure, Office 365, and more?

Come check it out. Cheers :)

(grateful for boosts)

https://www.youtube.com/watch?v=QVrcHv-Tm4k

maartenballiauw, 5 months ago to dotnet

We have a livestream coming up next year!

📺 Mastering OData: An In-Depth Developer’s Guide

🗣️ Speaker: @cwoodruff
🗓️ When: January 9th, 2024, 3 PM UTC
🤗 Open to all, welcome!
🎟️ More info: https://jb.gg/69rlcy

#aspnetcore #odata #apis #dotnet

bytefish, 6 months ago to dotnet

I have written an article on using Kiota to generate an API Client for an ASP.NET Core OData Service. The article also shows how to use it in Blazor:
https://www.bytefish.de/blog/odata_openapi_kiota_client_generation.html

#dotnet #fluentui #csharp #odata

jab, 9 months ago to CSharp

Oh the joys of working with #csharp and #dotnet

Here we got a class, in our regular #odata controller functions it produces #camelCase like we tell it to in our settings. However, in our non-base controller function it produces #PascalCase ... because, duck us?

Only on the expanded parts which are handled a little bit differently for efficiency, hense the need for the non-base controller function with odata.

Why, oh why didn't we do this with #graphql and something like #quarkus or even #fastapi?