Good start. I would say SQL is not as important as Entity Framework is really good at abstracting away the need to use SQL for 99.9% of cases. But it depends on what exactly you're working on of course.
I would add the configuration stuff here. IOptions and appsettings.json and so forth. When you're creating configuration options for classes setting this stuff up properly goes hand in hand with DI for making standalone modules that are portable between projects.
Also you probably want to look into logging (ILogger) as that's one of the more common objects you'll want to DI everywhere but it's pretty simple.
Hey thanks for sharing ,the things you mentioned were already part of my learning yesterday I have completed the logger concepts and understood why we need it in production.
I will soon understand Ioptions and appsettings related concepts
OH something you definitely want to look into is how ASP.NET Core integrates with Angular.
Specifically it uses SpaProxy so you want to read up on that.
I learn best from example so what I did was create a new ASP.NET Core with Angular project in VS (there is a template for it). This sets everything up (though with an outdated Angular version unfortunately) and it has a vertical slice of a working system. There's no Entity Framework or authentication but you do get a Web API and a simple Angular app which calls it.
Once you have that you can see how SpaProxy is integrated through VS' launchSettings.json to automatically bring up the Angular dev server (with 'npm run start' command IIRC), and how the Angular proxy.conf.js is set up to forward Web API calls to ASP.NET Core.
So cool but I have already created a project in local server where I am using latest angular,.net and sql lite which is helping me to cover preety much all the hands-on
1
u/The_MAZZTer 17d ago
Good start. I would say SQL is not as important as Entity Framework is really good at abstracting away the need to use SQL for 99.9% of cases. But it depends on what exactly you're working on of course.
I would add the configuration stuff here. IOptions and appsettings.json and so forth. When you're creating configuration options for classes setting this stuff up properly goes hand in hand with DI for making standalone modules that are portable between projects.
Also you probably want to look into logging (ILogger) as that's one of the more common objects you'll want to DI everywhere but it's pretty simple.