[dep_b]

Being a senior dev doesn't mean 20 years of experience on every part of the stack. It means you deliver value even when things get tough. MVC is so ridiculously simple compared to WebForms I don't even know why you wouldn't sell yourself as top of the bill senior for projects that are MVC based.

[HigginsNinja]

I agree with you, but there is still convincing hiring managers that it's okay to hire someone who technically doesn't have professional experience in ASP.NET MVC when the position is primarily that.

Here is a company I have worked in. They have legacy systems that are pretty heavily Web Forms and there is a lot of SQL work too. They are making the transition to MVC and ORMs in a lot of the legacy stuff.

http://careers.stackoverflow.com/jobs/75235/principal-softwa...

Hope it goes well for you.

[RefactorCareer]

I guess because I don't really have the experience of things going wrong there. I can tune a troubling sproc into performing well, but that won't make me seem like a senior dev when EF isn't syncing with an autogenerated db properly and I haven't been through that scenario before.

I'm honest with myself about what I know and don't know, and I'm willing to work on side projects on my own to learn more if I felt hiring managers would count it for something. I'm just at the crossroads of what I should try to focus on next.

[scarface74]

MVC is a lot easier for someone who grew up developing on the web. But if you aren't skilled at hand rolling your own HTML and you don't know client side frameworks that can take the place of the bloated but easy to use WebForm controls, MVC is a lot harder. WebForms hide the real web from developers.