Check out my courses: and use code LAUNCH for 15% OFF any course
Become a Patreon and get source code access:
Hello, everybody, I’m Nick, and in this video, we will take a look at the brand new NativeAOT support for .NET APIs. We will see what’s supported, what isn’t and how, by using it, we can achieve 10 times faster startup times and 10 times smaller application size.
Workshops:
Don’t forget to comment, like and subscribe 🙂
Social Media:
Follow me on GitHub:
Follow me on Twitter:
Connect on LinkedIn:
Keep coding merch:
#csharp #dotnet
This is mainly usefull for command line programs, and IOT EDGE modules on memory constrained devices, or devices that update over slow 3G cellular.
Hi, how to make my terminal looks like yours?
Very cool! Which console are you using?
Anyone know if Complete Course Bundle will also include a future courses or just the released ones?🙂 Btw. Thank you for your videos on youtube Nick.
Why is everything "INSANE" nowadays? Technology develops, things get smaller, small programs used to be small. NativeAOT does exactly what it advertises. How is that "INSANE" in all-caps? I would call it insane if it would NOT perform how it performs.
Great video, Nick! Have you considered whether Native-AOT supports Linux? It could be beneficial for containerized applications if it's faster than AKS. What are your thoughts on this?
Going to use it for AWS lambdas
👍
this would be way more popular if there was a transpiler/scaffolding tool that found all everything that used reflection and implemented an alternative automatically or if none existed provided meaningful error explaining which calls that will fail (and line numbers of course)
Well, we could be expert at other languages such as Go until we have full support for AoT and have these things much sooner 😛
use autocannon to compare the diff…
Does this work with EntityFramework?
hi Nick, thanks for very interesting and informational video. But let's imagine what in some minimal api project type which contains a lot of http clients and serialization flows (as example 5-6 different serialization models) . Now do we need to create each time (5-6) json serializer context(s) and register in start up? Or it not relevant to do? Thanks
How to do the 4:57 implementation in Visual Studio 2022 community?
Why will anyone use GO after this feature is fully supported. Learning GO was amazing but using it not that much. I guess I will stick with c# for a long long time!
Тhanks Nick. I thick you should start making your videos on mac or linux since so many people have questions about supporting other platforms except windows
gRPC support is already enough to start using this feature. Very interesting.
How does it affect integration testing? You need to change your code in some cases as you said (reflection). How do I test that using automated testing? Can you run integration/unit tests against native code? If so, do you still need to change how you develop/run your tests (IDE tools, additional workarounds)?
If I can't develop automated tests to make sure my code works, that is a big deal breaker for me.
Feels like a huge improvement for the future of serverless with this greatly reduced start up time. Really looking forward on how serverless will evolve in few years.
I'm wondering why did you mention docker and native compilation in one sentence. Is docker still necessary for AOT compiled applications?!
I was about to try NativeAoT for a tool on the ATM which is pretty slow
Nick I have other question. Is your chair good for long work on computer ? I see that it is gaming chair. I found a lot of info that only ergomonic chair can be comfortable. Thanks in advance for asnwer! 😊
My face after watching 5+ minutes and slowly realizing that I confused AOT with AOP.
i think this is great match with azure func or aws lambdas where you are penalized for cold start significantly
what about some big projects where a lot of serializable objects? What about their memory and startup time?
Amazing 😻 Waiting for your example with AWS lambda web api, especially in case where your lambda should consume your own nuget packages from Code Artifact.
Yeah #dotnet10 as you say, that'd be grand. :-). Great video Nick!