Is ASP.NET Core Now a Mature Platform? (rehansaeed.com)

I've done a few projects using ASP.Net Core and they've used all of those

- Autofac - Automapper - EntityFramework Core - MassTransit - MediatR - Moq - Newtonsoft.Json - NodaTime - NUnit - Quartz.Net - RabbitMq.Client - RestSharp - Serilog

The only thing we use .NET Framework applications for is Windows services through our use of TopShelf since it does all the heavy lifting surrounding windows service's lifetime management. All our other apps are .NET Core though.

We build a lot of CQRS / DDD style applications, and the above list covers us off pretty well for our architecture that uses RabbitMq for messaging.

Would be interested to know which packages you are missing?

Though you can basically use any editor.

VSCode works, but I enjoy Rider.

Can't stand Windows, and Visual Studio is pretty terrible as well (IMHO), it always freezes on my beefy hardware (32 core threadripper, oodles of RAM, NVME, etc).

https://github.com/fluentmigrator/fluentmigrator/issues

I am curious about your encrytion scenario and why did .Net core fall short.

This point drives me mad. Only after running into errors and reading SO you discover some methods should be called before other. Given how many there is, it's difficult to know if the whole order is done right.

> There are no tutorials on how to add Vuejs or React to your asp.net core project.

This is a remarkable complaint to make. There are literally template starter projects for react/angular when you go to file -> new project. If you choose not to use a starter template, adding your own frontend is trivial: place the built frontend in wwwroot and have an MVC endpoint that returns index.html. I’m not sure how this could be any easier, and it makes me wonder if you ever used .NET core at all.

> Postgres is simply treated as "not important" and you are expected to use mssql. 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.

This is simply false. I have used Postgres with .NET core extensively and have never been forced to fall back on SQL server. Exactly what are these serious issues?

> Only tutorials available teach basic stuff like middleware, rest api without authentication.

Are you complaining about setting up authentication? It is easy to add JWT support in startup.cs and then secure endpoints via attributes.

> 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.

What’s ugly about it? The DbContext represents a particular database connection and a DbSet represents an entity within that database. That’s an entirely rational way to represent the data layer.

> Need image processing libaries? Good luck with that. There is simply no support.

Another remarkable complaint to make. Nothing apart from OpenCV, ImageSharp, the native System.Drawing package, and this entire list of options: https://blogs.msdn.microsoft.com/dotnet/2017/01/19/net-core-...

You should really stop making claims about .NET core that are demonstrably false.

    using DotEnv = dotenv.net.DotEnv;

        public static void Init()
        {
            var levelsToCheck = 4;
            var currentDirectory = new DirectoryInfo(Directory.GetCurrentDirectory());

            for (; currentDirectory != null && levelsToCheck > 0; levelsToCheck--, currentDirectory = currentDirectory.Parent)
            {
                foreach (var fi in currentDirectory.GetFiles(".env", SearchOption.TopDirectoryOnly))
                {
                    DotEnv.Config(false, fi.FullName);
                    return; // found .env file
                }
            };
        }