So many cool tools, which way to go…

I was beginning to work on a new exploratory project where I wanted to get a little deeper into some technologies that I don’t get to use every day at work. I’ve got a plan to build a cloud-based web site that does a few things.  So the choices were Angular or Aurelia on the front end and Node or ASP.Net 5/MVC 6 on the back end.

I’ve been doing various Node and Angular exercises and tutorials for the past year or so and have also been excited about the release of ASP.Net 5 and what it promises.  Although I’ve been put off by the recent Node schism, I’m fully confident that either a reconciliation will take place or IO.js will run away with the ball.  And the Node/IO community is so incredibly vibrant right now.  It seems like there’s a package for anything/everything. You can literally see the energy coming off of that system. Recently, I’ve also been impressed by the Aurelia project and it’s embrace of ES 6 and other emerging and established standards.  Aurelia will probably be a niche player in the SPA market when compared to Angular/React/Ember etc…, but it’s a really cool and looks well put together, so why not try it out.

But as cool as Node is, there are things that I’ll miss terribly in the .Net ecosystem like LINQ and (a hopefully more performant) EF and truly awesome productivity tools in VS and R# as well as all of my previous experience. I also want to support .Net’s move into OSS and embrace/trust its own community.  Already the source code out on GitHub has been an incredible help to me.  I think that’s already paying off.

I’ve decide to stick to my .Net roots and try out Asp.Net 5/MVC 6 as an API on the backend, trying to learn it while it’s still relatively new and attempt Aurelia on the front end with help from Bootstrap.  We’ll see how it works out…

2 thoughts on “So many cool tools, which way to go…

  1. mvc + aurelia makes no sense in my opinion. You have razor pages and for what do you use aurelia? 😉 I will use web api with restful service + aurelia.


    1. Hi bastienJS, thanks for commenting! If you were referring to ASP.Net as it stands now, I would be with you, but this article refers to ASP.Net 5 aka vNext and MVC 6. Web API doesn’t exist anymore in ASP.Net 5. It’s now rolled into MVC 6 and is just another way of rendering the model much like a lot of other MVC frameworks out there. So instead of applying a view, you just render an ObjectResult which can return JSON/XML/etc… See here for a good example:, or you could just look at one of my follow up articles 🙂 Of course ASP.Net 5 only just recently reached RC status, so the walkthrough may need some tweaking as it was written a couple of months ago.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s