So at work we use ASP.NET web forms. Since the .NET Core exists now, and that uses ASP.NET MVC, is it worth looking into that and learning about it? My boss is hesitant to move over for our next project because web forms will go faster because we don't have to learn something new.

@g-m-f Okay. We are stuck on an existing project for a bit, so if I see an improvement while I toy with some side-projects, I'll probably try to change his mind so we move over for the next one.

@DevotedSniper Never used MVC at all anywhere, because I'm still in college and this is a part-time job on campus. I'll still probably check it out, and since I have access to pluralsight through work, I will probably try out a course there.

We made the switch to MVC a few years back and it's definitely worth it. The application structure is just so much more logical and makes maintaining and development much less effort due to separation of concerns.

I also agree with everyone else's comments that it's a steep learning curve and is difficult at first to get your head around. So initially you'll hate it but stick with it and once you get it you'll never go back.

Why not making a full leap and move to a spa+web api?

By spa i mean reactjs, angular, vuejs

There's more leaning curve than moving to mvc (mainly because of language javascipt/typescript) but could be more profitable in the long run

@searchindex eh. I tinker with js already, but this is a secure job with regular raises built in with a great mentor. I'll still learn it on my own time probably in the summer, but for now I'm sticking with Microsoft's stack.

@shortstuff I do side projects in more modern technology, I'm okay. It's low pressure, flexible schedule, and better than any other employment I found in this college town. It's better than the red lobster jobs the rest of my CS buddies have to do