4 ms·
With .NET Core 3, you can deploy them standalone, and performance is much improved. So you might have a happy middle ground available now. And when I say perf
by gameswithgo 7y ago
With .NET Core 3, you can deploy them standalone, and performance is much improved. So you might have a happy middle ground available now.
And when I say performance is improved, there are two fronts to that. First, the compiler/jit are just better now, core library functions are sped up a ton, so just running ported old .NET Framework code will be a lot faster. But also, C# has added new features in recent years that give you further control over memory usage/layout, and now even SIMD Intrinsics, so the performance ceiling is much higher if you want to optimize your own code.
- huzaif 7y agoPiggy backing on this a bit.. You can now publish a .net core 3.0 app that is: 1- Ready to Run: Part AOT compiled app for the platform. 2- Trimmed: Tree shaken down to only necessary bits from the framework. 3- Single File: Self contained app. This combination of features provides a really decent balance between size, performance and distribution.