Ask HN: How do I get back into .NET development?
I'm 38 and started my developer career 15 years ago. 10 years ago I switched from .NET to Golang. And for the past 5 years I have primarily worked with mobile apps (Kotlin/KMP) and transitioned more into a manager role.
Now I'm looking to focus more on the coding and I'm interviewing for a senior .NET backend position tomorrow. I'm hoping that my experience in the field will make up for most of the .NET-specific things I have missed or forgotten about. Do you have any advice on what I should prioritize to read up on before the interview?
I will very much appreciate any suggestions, thank you!
14 comments
[ 3.0 ms ] story [ 50.1 ms ] threadBut specific to .net would be 1. Asp.net core MVC pipeline 2. What are new changes or improvements in .net 6/core 3. Dependency injection 4. Authentication - JWT, OAuth, Cookie based. 5. What is middleware and give me few example where you would use this?
Also most probably they will ask about Azure specific services like 1. Service bus concepts 2. Queues 3. CosmosDb 4. App service 5. AKS - managed Kubernetes.
C# concepts - Interface vs Abstract class, Collection interface differences like IEnumberable vc ICollection vs IList, when to use what?
Hope it helps, Good luck!
This is going to be annoying to learn about.
If anyone has a good summary, please send, cause I don’t know of any, and it’s complicated.
.NET Framework was the .NET we all knew and tolerated. It was on version 4.6/7 or so. Windows specific, requires a full install of the framework on the machine to run. Support for Winforms, WPF, WCF, Webforms, ASP.NET MVC/API etc.
Microsoft wants to make a play for the cloud. Windows Server is expensive and no one likes it. Luckily for Azure OS is irrelevant, whichever server Microsoft still gets paid.
Step forward .NET Core. This takes the .NET runtime and makes it cross-platform (and open-source). Only really supports ASP.NET in the beginning. There are some libraries/APIs that are available in both .NET Framework and .NET Core runtimes. This common interface is .NET Standard, you can basically ignore this now I think but it means libraries can be used from both.
.NET Core goes through multiple versions, 1, 2 and 3. More things are ported to .NET Core but Winforms, WPF and Webforms are left behind. Meanwhile Core becomes a better and better platform for web servers.
.NET Core drops the 'Core' naming, becomes .NET starting at .NET 5. .NET Framework is legacy but gets a bump to .NET 4.8 or so. So basically unless you're doing Winforms/WPF/Webforms you can be on .NET Core/.NET 5+ with minimal issues. Hopefully that clears something up.
Note that .NET Core 8.0 is about to be released so you may wanna start with that at this point.
https://learn.microsoft.com/en-us/aspnet/core/?view=aspnetco...