Using it for two days now on OSX for a client so I don't have much experience with it. First impressions are ok, the documentation could be better and it's not very googleable as you get a lot of irrelevant hits from normal .NET, MS really should have more creativity when it comes to naming. Problems I've hit which I wouldn't expect to hit in a more mature framework:<p>* Running EF Core migrations against postgres on startup. I wasn't able to google a solution to this. I hacked around this by deploying an init container with a migrate.sql script but I expect that'll bring me problems later on.<p>* Let's Encrypt. Found an archived package on GitHub, I expected more maturity.<p>* Not very easy to ascertain the state of the setup, things need to be registered in a certain order for them to work (UseDefaultFiles & UseStaticFiles f.i.). This would be made easier by me having more experience with the stack or better docs, still a waste of time.
Yes, Bing runs on Asp.Net Core: <a href="https://blogs.msdn.microsoft.com/dotnet/2018/08/20/bing-com-runs-on-net-core-2-1/" rel="nofollow">https://blogs.msdn.microsoft.com/dotnet/2018/08/20/bing-com-...</a>
I've been developing ASP.NET Core website for 1 year. Now my website runs on production. It is easy to customize, fast and reliable platform. Microsoft makes a lot of efforts to add new features to it. So I definitely advise to use ASP.NET Core.
We run the core of our order system on dotnet core, including (somewhat) micro-service architecture behind the scenes. Build on primarily windows desktops, and hosted on Linux containers. Works well for us; there are a few things we needed to roll ourselves, but by and large it works out of the box.
<a href="https://webcache.googleusercontent.com/search?q=cache:3OI6s-GBQPwJ:https://rehansaeed.com/is-asp-net-core-now-a-mature-platform/+&cd=1&hl=en&ct=clnk&gl=sg&client=firefox-b" rel="nofollow">https://webcache.googleusercontent.com/search?q=cache:3OI6s-...</a><p>Google cache cos it appears the site is down at the moment :(
Third party support bugs me for .Net Core but otherwise it has been amazing. For example, I had some problems using it with Firebase and other than SignalR there doesn't seem to be another websockets library present.<p>I mainly develop on Ubuntu using VS Code & Docker.
Are there any open source projects that are representing all features, like an admin panel with an API? As someone coming from Java and Rails, I can learn it with just reading the code.
I'm running it in production on pretty large website for about 6 months now, no issues so far. Performs very fast as well.<p>Also, I develop on MacOS using VS Code most of the time.
The main pain points for me regarding .NET Core has been the lack of third party libraries, hard to understand sometimes which project can run on .NET Core and several cases that I had to switch back for smaller projects in order to use a specific library.<p>.NET Core is great, but I would continue to run it on .NET Framework for now.
I also use asp.net core both for personal project and company product. It works great especially with f# and giraffe. But in company we use oracle, the devart.data.oracle.efcore is not very good, actually a little bad.
I find it striking how many of the blind spots wrt the web have been a feature of ASP.NET since the beginning: static file serving, caching, authorisation...
One cold harsh truth is that Asp.net core is nowhere close to node, python or django when it comes to libaries.<p>It's growing but not that fast.<p>C# is very verbose compared to Ruby. You'll find it hard to get Rails level of productivity with Asp.net core.<p>Why? Because there is no sidekick, actionmailer, or asset piplining, turbolinks.<p>Stuff like, "has many, through" (Rails) relationship isn't supported in entity framework. If you plan to use postgres, you'll run into many issues.<p>You end up dealing with ugly DbContext for setting up basic models. And DbSets to enable tables for your models. All this ugly stuff is thrown in your face.<p>There are no tutorials on how to add Vuejs or React to your asp.net core project.<p>Postgres is simply treated as "not important" and you are expected to use mssql.<p>PostGres + Entity Framework Core is mostly a hack. You run into soo many issues that you'll be forced to leave Postgres and go for mssql.<p>Need image processing libaries? Good luck with that. There is simply no support.<p>The only thing you've going for you is, static typing and cool IDE support.<p>I tried asp.net core for several months and went back to Rails.<p>Lookup ActiveMerchant and how many payment gateways it support, there is nothing like that in Asp.net core.<p>Don't get me wrong everything is possible in asp.net core but you'll have to hack together your own solution, there is no standard way of doing things like there is in Rails.<p>There is a very good reference project: Discource if you want to see the potential of Rails.<p>Where can i find reference project for asp.net core? There are no good books either.<p>Only tutorials available teach basic stuff like middleware, rest api without authentication.<p>Heck all that can be done in Flask in 10 lines.