Navigating the .NET Ecosystem for Backend Development

I absolutely love C# and recommend it! If you're unsure about the concepts, just take it step by step. I suggest going for a minimal API style; it's more efficient and aligns with the future direction of .NET. When choosing between EF Core and Dapper, think about whether you prefer writing classes to shape your database or handling SQL queries directly. And remember, testing frameworks are mostly a matter of preference, so pick the one that feels comfortable for you!

It's good to see you're considering your options! The multitude of choices in .NET can feel daunting, but it's a blessing in disguise. Most projects can benefit from different tools, so you're not stuck with something that doesn't fit. Just pick one path to start learning; the fundamentals of C# will remain relevant no matter what you choose to dive into.

If you’re feeling overwhelmed, starting with an MVC app using Entity Framework Core could be a solid choice. Even if you're planning to build an API, you can skip the views and just focus on models and controllers. There are tons of tutorials that can guide you through this process! Just remember, if your project doesn’t need scheduling, you can ignore the Hangfire vs Quartz debate.

Have you checked out Blazor? You can create multi-project solutions that incorporate Blazor for your front end and APIs for your backend! It could be a cool way to balance everything you need.

Don't forget that PHP has a range of frameworks like Laravel and CakePHP, but Laravel often takes the spotlight for its extensive features. Just keep in mind, the scenario isn't all that different with Go; it has its own ecosystems too. If your heart is set on C#, dive in; learn the basics of OOP first, and you’ll find your footing in any framework.