problems and building numerous console projects.
Then I learned the basics of C# and Winforms.
I learned the fundamentals of relational databases and SQL Server.
I also studied the basics of ADO.NET as a data layer.
Now, I need to learn ASP.NET.
The problem is that all the courses I've found assume that you already know HTML, CSS, JS, and Bootstrap.
This approach makes sense for content creators who want to target a broader audience, as most people now start by learning front-end before moving to back-end development.
However, why do they complicate it by including something beyond the course's scope? While it's necessary to use HTML and CSS in a web course, why make it more complex by focusing on design?
So, I think I should start by building an API. The issue is that they still overcomplicate it by using the MVC pattern, Entity Framework, and dependency injection.
Entity Framework is okay, as I can learn it separately. But why is it required to know dependency injection in a beginner's course? as I know Design Patterns are typically solutions for common, complex problems that can be addressed with a generic solution . As a beginner building my first web app, I haven't encountered these problems yet or fully grasped what they are. How can I understand the solution without understanding the problem?
Are these issues unique to me, or are they common in the .NET community? Any advice or suggestions?
if you are new to mvc, efcore as well as html/css/js then it will definitely be overwhelming. I recomment starting mvc with your own way using ado.net having basic bootstrao then proceed
Обсуждают сегодня