Tiny, fast ASP.NET Core APIs with native AOT | .NET Conf 2023

[@QINGCHARLES]

@dotnet Sending Damian a hug🤗I felt so bad for him when it wouldn't build live in front of the world. We've all been there😂

[@jarosawfrankowski7845]

Great introduction to AOT, Damian that was great presentation! 😊

[@alirezanet]

About the demo issue you had, I think you just forgot to save your csproj file 😊 (usual live demo problem)

[@hero3616]

That is correct

[@jim2lane]

Exactly - live demo, what could possibly go wrong? 😉

[@realivanjx]

i hope blazor server gets native aot support asap! nice work!

[@idzyubin720]

@dotnet Great explanation! Is there any link how can I validate request model in Minimal API with Native AOT?

[@BredoLab]

Can somebody explain how Native AOT is beneficial for server-side apps and minimal API in particular?

[@jinhuisong8727]

For example, AWS Lambda or Azure Function , all of these serverless apps had cold start. The cold start will take lots of time to let code ready. Java or C# maybe take 1-3 seconds, python only use 500 milliseconds. Use AOT C# also can use 500 milliseconds for cold start.

[@freddydev3562]

xdxdxd@@jinhuisong8727

[@alex22932]

Also where you can scale containers to zero such as Azure Container Apps and Google Cloud Run.

[@serverlessjames]

If you want to see this in action with .NET and AWS Lambda I've got another video on KZbin. Crazy cold start numbers. kzbin.info/www/bejne/oarFYmmoYrSoopI

[@Sindrijo]

C# app normally is distributed as IL-bytecode (Intermediary Language) that when 'executed' the environment first has to load the CLR which then will compile the IL-bytecode into native code/instructions that then gets executed. With AOT this final compilation happens 'ahead of time' avoiding the previously described steps of loading the CLR and compiling the IL-bytecode to native code, instead the code just gets executed immediately.

[@benyahiahassen4540]

About the issue you had, you should change what you wrote in the config to true not true