✅ .Net Core
In many job postings, they mention "Good understanding of ASP.NET Core technologies." What does this mean? Does it imply knowing how to build a Web API, work with ASP.NET Core MVC and Razor pages, or is it a completely different thing?
27 Replies
Most likely.
You'd have to ask them about it.
With how many things are contained under the "ASP.NET Core" moniker, it can be anything from minimal APIs to Blazor WASM
Now, thankfully, all of those share certain similarities
So even if all you know is MVC, jumping into Minimal APIs or Blazor won't be too hard
Best thing to do is ask.
Definitely. yeah
So, my plan is to go through these three courses:
ASP.NET Core 7 - https://metanit.com/sharp/aspnet6/ (started like week ago)
ASP.NET Core MVC - https://metanit.com/sharp/aspnetmvc/1.1.php
Razor Pages -https://metanit.com/sharp/razorpages/
Of course with additional content (courses are just like mini-roadmap inside tech for don't learn random things), building projects on each tech. and only after to email some potential employers, will this be enough to say "I know basics of Asp.net core" or this is just waste of time and better to go other way?
Microsoft
Learn ASP.NET | Free tutorials, courses, videos, and more
Free courses, tutorials, videos, and more for learning web development with ASP.NET. Resources from the .NET team, .NET community, and training companies.
I mean, when you're scrolling through job listings, you can't just email every employer and ask what specific tech skills they require, and then respond with "I don't know that one", am i wrong?
Email one.
Most of them require the same skillset.
When I read this I think they expect knowledge of common concepts and patterns from an ASP.NET Core perspective.
As long as you know the basics it's most likely fine.
If you can pick up on stuff decently fast that's a bonus.
Would you consider basics to be "good understanding" though?
Might be semantics
But the job posting would hopefully help clarify their expectations.
No, but it's good enough.
I'd argue that the position being applied for impacts that.
For a junior position sure
Companies lie and hassle whenever they want, why should we not do the same?
For an intermediate level position I'd expect more than the basics
Expectations versus reality.
i mean, it always like this -
SOAP? Nowadays?
¯\_(ツ)_/¯
They should add the KISS principle.
CSharp 11?
Old, old & old.
I'm not an expert in ASP.NET, but I'm a lead developer in a professional capacity. If I were evaluating candidates for an ASP.NET position, I'd have a checklist that reads out something like this:
Experience With:
- Routing
- Controllers
- Views
- Razor Pages
- Dependency Injection
- Middleware
- Logging
- Error Handling
- Testing
Knowledge Of:
- Entity Framework Core
- Deployments
- Hosting
- Middleware Pipelines
- MVC patterns
- Security Practices
- Swagger
- SignalR
- Serilog
The more boxes you make me check, the stronger a candidate you are
Hire me.
Yeah, gotta support legacy systems unfortunately.
Unfortunately :(
Okay, on a local site, everything is clear, and there are some super legacy technologies there. But where do people even look for jobs in 2023?
I have no clue at all.
LinkedIn
LinkedIn: Log In or Sign Up
750 million+ members | Manage your professional identity. Build and engage with your professional network. Access knowledge, insights and opportunities.