Let’s face it, ASP.NET Core is the new hotness.
Or as my mom used to say when explaining to her friends why she was buying me baggy jeans: because it’s in style.
To me, as someone who jumped aboard a 5-year-old old Web Forms Line Of Business app, Core gets me super excited in that geeky, shiny object syndrome kind of way that I get when Google launches it’s new Nexus phones.
My team just recently converted our app from a .NET 3.5 Website Project to a .NET 4.5.2 Web Application project, (mostly by following Dave Paquette’s great article) so when I heard about ASP.NET Core, I immediately wondered if we should go the distance and migrate again while we were ahead.
I feel at least somewhat identified as a .NET developer and for some silly reason, I’ve felt old, rundown, legacy. Watching all my peers whip up Node apps with using hot new frontend frameworks like React and Angular.
Not to say that Web Forms isn’t a perfectly viable solution, even today, but you just feel a bit of envy.
As .NET devs (devs in general, really), we love clean, minimal, decoupled code, and the idea of using new frameworks with those principles built into the very foundation is exciting.
And I think we have that with asp.net core.
But, I believe most of us can put our blinders on when it comes to asp.net core. I think that unless you are working on small personal projects, or new projects that will have a long lifespan with rapid adaptability, you can focus on improving or maintaining your asp.net web apps with the usual frameworks.
The obvious reason, it’s still new. When code is new, it can be unstable. And as we all probably know, stability is paramount for business critical apps.
- The ecosystem is just beginning to play catch up. As Core continues to stabilize and find its feet, the community can now grow around it (as you are seeing happen right now!). We love our libraries, and if you want to go full Core, you’ll find that many are missing.
- And my final reason, which is perhaps the most compelling, is that migrating an existing app to full core would be nearly rewriting your app from scratch. .ASPX is gone, so that nicely(?) coupled page/codebehind style we currently benefit from has gone the wayside in favor of the decoupled MVC paradigm. You’d essentially be converting your app from MVVM to MVC in a sense, if you’re working with WebForms like myself.
Those are the main reasons I’ve come up with. What others can you think of?
Again, I’m really excited for Core. As a side project, I’ve started a personal budgeting web and android app that will run on Core and hopefully I’ll have some stuff to write about along the way.
Hopefully that was helpful, I’d love to hear what your thoughts are (tweet me), and if you enjoyed, please share the post url! :)