I am unsure how to go about learning Entity Framework Core.
That might not even be the part I'm having the issue with, though it is an issue. I've been trying for the better part of 2 months to make some kind of headway into ASP.NET, or Entity Framework Core, or Razor, or... whatever these things are and whatever it is they're trying to accomplish. I have not been able to find any information friendly enough to my lack of understanding of what any of those are to learn the basics. The Microsoft tutorials seem to assume I have information that they didn't bother to teach, and I'm sure we could all commiserate on the variable quality of YouTube tutorials. Can anyone please point me in the direction of, like, the super easy ground level for babies introduction to EF Core or Razor or... whatever it is I'm missing that isn't permitting any of this to click?
21 Replies
how much u know of c# in general?
normally you would start with the fundamentals
C# Fundamentals for Absolute Beginners
Learn C# programming from an expert in the industry. Get the tools, see how to write code, debug features, explore customizations, and more. For newer videos head over to dot.net/videos
using console applications and practicing doing actual projects...
Learn OOP which is also very important
and only then u would climb into a specific stack
and even so you might look up things before u do
like in asp.net core case, I would further look up things like Dependency Injection and learn it before going into it
and how the Hosting api works
I followed the c# track enough to get the certification, I have a workable ‘can find out what I don’t know’ level of competence there. I’m ok with backend console line type stuff, but that’s about it.
I followed the c# track enough to get the certificationfrom where certifications nowdays are pretty much worth nothing specially online ones with all the llms out there
I have a workable ‘can find out what I don’t know’ level of competence theresure you can spend hours looking for the right thing or just learn from the fundamentals and up and waste less time trying to pick what is wrong every time u find an issue for things u didnt go by... doesnt sound very efficient depending on your level of knowledge which I dont know where its at... as one example a lot of people go into unity without learning c# and think it will be easier to just learn with unity, and fail for the most basic things like access modifiers and scope of things.
Well, you got me in so far as I did start with Unity, and it didn’t really help it click. I got the certification from the Microsoft learn pathway, which I figured would be as good a place as any to get a handle on the basics.
As for my skill level, I could write a simple console app under my own power (make little menus, save and load data to files, navigate to directories from the command line) and literally nothing else. Ok, not literally nothing, I know like 5 HTML tags.
well the basic learn path way is very very basic
doesnt go into a lot of important subjects
so u need to further complement that with more of the content they offer
such as the video I pointed above
which also doesnt cover everything sadly
from there u want to learn OOP at least
and beyond that, depending on what kind of path u want to follow i.e.: web path the other things I mentioned
other things u also want to learn for web is say how to use postman, how requests and http works
so yeah each path will have their distinct things u will want to learn
to learn efcore for example all u need is a console application
but ideally you also want to know about SQL
because in the long run you will need it to understand how to best take advantage of things and optimize it
As for my skill level, I could write a simple console app under my own power (make little menus, save and load data to files, navigate to directories from the command line) and literally nothing else. Ok, not literally nothing, I know like 5 HTML tags.then I would suggest you try picking $projects here and see how far you can do these projects without help of AI with just what u know
Collections of application ideas that anyone can solve in any programming language to improve coding skills:
https://github.com/dotnet/dotnet-console-games
https://github.com/karan/Projects
https://github.com/florinpop17/app-ideas
and then post back either to a new #help thread asking what u can improve what u lack or #code-review
but do it until u complete it with what u know
start with easy ones and move up to medium difficulty
that is great to assess how well you're doing
Holy heck, I knew there were more resources out there than I was finding. Thank you very much, I’ll take a look at these guys and see what skill deficits I run into.
sadly in programming there is no special recipe of learn this in 24hrs, it has so many variable in the way such as how well a person digest the information, practice it and learn it and understand how to put it to use, the specific path they want to learn, etc
no worries there is also $helloworld which have more links
Get started with beginner tutorials
- Interactive text tutorial
- 5h intro course
- Video tutorial
- Fundamentals documentation
the important thing here is do not use AI at all, research and learn on your own
got stuck?
we are here just open a thread and ask away
relying on AI to learn things you dont know or can't validate is a massive pitfall
Alright, so what I’m getting from this is get the C# fundamentals down until I don’t have any more questions there, then move on to… something. Which was another issue, because after I got to my current level of skill with c# I figured the next thing to do was look for context in which to use it.
Alright, so what I’m getting from this is get the C# fundamentals down until I don’t have any more questions there,yes, specially debugging that will be your friend for life
then move on to… something.then learn OOP, which is everywhere in the language then you move on to something which imo is creating actual projects to see how you're doing with what u learned u can't just be reading things you need to actually put them to practice because otherwise it will just vanish from you one way or another even we that do it daily forget things we dont use often the difference is if we used it to some extent it will come back easier to us once we touch it again but its still a stretch once you done some projects you will see how well you understand of the fundamentals, oop, and say u want to go into web I would strongly suggest you at least learn about Dependency Injection and Hosting api for a start because once u create a web project those 2 things will be thrown straight to your face first thing and they are confusing if u dont know how they work.
In addition to all that was posted above, there is also...
$helloaspnet
Get started with ASP.NET Core
A short tutorial using the .NET CLI to create and run a basic Hello World app using ASP.NET Core Blazor.
and $helloef
Getting Started - EF Core
Getting started tutorial for Entity Framework Core
I would suggest learning one of these at a time to start, doing both at the same time might be overwhelming
and start tiny
and to try and answer
or... whatever these things are and whatever it is they're trying to accomplishbriefly... ASP.NET is the default web component of .NET. It can be used to make web apis (pure backend), server side rendered pages (backend+frontend, often uses razor which is a server-side rendered frontend template), reactive pages using Blazor (a razor variant, can run either server or client side, or both) and a whole load of other stuff. If your core idea is to communicate using HTTP(S), ASP.NET is probably where you start. EntityFramework, aka EF, these days commonly called EF Core, is a database ORM, object relation mapper. An simple way to reason about this is that it can bind an object, usually an instance of a class or record you made yourself, to a row in a database. You can query these from the database, or insert new ones into the database. Changes to the object can be reflected in the database if you so wish. Using EF Core means we dont need to write the raw SQL statements ourselves, we just use fluent syntax to describe what we want and EF handles the rest. As an example, this is what a simple query could look like with EF.
This is all excellent information that's pointing me in the direction of being able to learn those 'don't know what I don't know' kind of questions. Thank you very much.