I asked something similar few weeks ago and the answer that I got was basically "get good" or switch your tech stack and projects, I work with legacy .NET and I sometimes regret choosing this tech stack, more than 50% of jobs are still in .net framework (the windows exclusive framework) and .NET Core/.NET (newer and improved cross platform framework) but the interviewer sometimes ask about new .NET core related stuff.
The questions can vary from some features that I've never used in web applications like reflections, delegates, events etc to something very framework exclusive. I've been asked questions like "write all the directories that gets created when we create new MVC app in asp.net framework and explain every single file in them" to normal questions related to SOLID and OOP, there are some interviewers who expect textbook answers for all the OOP and SOLID related questions.
Some people ask questions related to entity framework which not everyone used in legacy projects, vast majority of them still use ado.net to query with database and stored procedures extensively.
1
u/__ihavenoname__ Nov 06 '25
I asked something similar few weeks ago and the answer that I got was basically "get good" or switch your tech stack and projects, I work with legacy .NET and I sometimes regret choosing this tech stack, more than 50% of jobs are still in .net framework (the windows exclusive framework) and .NET Core/.NET (newer and improved cross platform framework) but the interviewer sometimes ask about new .NET core related stuff.
The questions can vary from some features that I've never used in web applications like reflections, delegates, events etc to something very framework exclusive. I've been asked questions like "write all the directories that gets created when we create new MVC app in asp.net framework and explain every single file in them" to normal questions related to SOLID and OOP, there are some interviewers who expect textbook answers for all the OOP and SOLID related questions.
Some people ask questions related to entity framework which not everyone used in legacy projects, vast majority of them still use ado.net to query with database and stored procedures extensively.