Used .NET Core for a while? What are your thoughts about it?

zinta pritie

My team is considering a few tech stacks at the moment for web development (Elixir, Clojure, TypeScript+Node, and .NET Core). I'm interested in hearing from folks who have used .NET Core for a while. What has gone well? What hasn't? If you could start your project over, would you still use it on the back-end? If you've stopped using it for web development, what are you using instead?

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Navaneeth Krishnan6y ago
https://www.biztechcs.com/blog/6-benefits-asp-net-core-enterprise-applications/
Varun Setia6y ago
Hi,

Please go through this.

Few Points for ASP.NET Core:

1. DotNET Core is fast, check the benchmarks. https://www.techempower.com/benchmarks/#hw=ph&test=plaintext
2. It supports Linux and Windows that makes it cross platform.
3. It is open source. You can see source code to dive-in deep: https://github.com/dotnet/aspnetcore
4. It has built-in Dependency Injection Container.
5. It has support for Docker.
6. The deployment size is small making it Cloud First. There are 2 types --> Self-Contained (no runtime install required) and Framework Dependent (requires separate runtime installer and size of deployment is small).
7. Only install those packages that you need, everything is imported through Nuget, making it small.
8. For modern architecture, we can use ASP.NET Web API as backend and Angular/React/Vue or Standalone Blazor Project that can replace Javascript with C# for SPA application.

Overall, it is being adopted fastly for Enterprise-size Projects. It gives us same C# for usage with high-performance apps.
Vinodh Palaniappan6y ago
.NET CORE has come a long way since inception, starting from Version 1.0 to 3.1 (LTS Version). Microsoft has made their intensions clear with .NET CORE, that it will play an important role in .NET stack in the days to come.

We have been using .NET CORE from 2.1 Version onwards. Its going to be like 2 years now. It has met all our needs to develop the product. It has its CLI's which helps us to fasttrack the work. And yes ofcourse, you have Visual Studio which gives a edge on using .NET CORE effectively.

Strong community presence to get all the help you need while development.
Good documentation and Reference material provided by microsoft to help you get started.

If you have already worked in .NET Stack, you will defenitely enjoy .NET CORE.
Their build engines are really good and fast.
.NET CORE is available in Azure and AWS platform and the future holds good for .NET CORE

The .NET CORE stack holds good for small to large apps, as .NET is in the industory for very long time.
If your building a product and thinking the tech stack should be relaible for more than 5 years, you have to pick a stack which is long running and not something which has created a buzz in the last 2 years.

We have had experience of picking new technologies because of the buzz created around it and had challenges when it came to real implementation. So think on few parameters before choosing the stack.
Community Support
Longevity (Past, Present, Future) - look at its past, thats very important to know, if the tech stack is matured or just a buzz because of some of its cool features.
Companies backing it
Events happening around the Technology
Supported Tools
Packages Support (like Nuget, NPM, etc)