Where I work, we develop and maintain a number of ASP.NET 4.5/MVC 5 web applications that support internal business processes/workflows and allow our clients to access timely information about the firm (data, reports) via a portal.

Since Microsoft announced ASP.NET 5/MVC 6, we’ve been busy researching the new features and benefits and wondering how we go about upgrading, as ASP.NET 5 seems to be a big change in how developers write web applications using .NET.

As of writing, ASP.NET 5 hasn’t been officially released so obviously it’s going to take us a while before we go into production, but I thought I would jot down some notes to help prepare for the transition and post about some of the issues we come across during the upgrade process.

The web apps are currently developed using Visual Studio 2013 and TeamCity (8.0.5) is used for our continuous integration build server. After passing QA they are deployed out to internal Windows servers running IIS or externally to Microsoft Azure. They’re also constantly in development (new modules, improvements to existing processes/workflows, performance tuning, etc…) so if we want to stay ahead in the world of .NET web development upgrading to the new platform comes part and parcel.

I’ll be updating this post/blog regularly during the upgrade to ASP.NET 5, so be sure to check back if you’re on a similar journey. Hopefully we can share some best practices and make the most of the new features.