These are exciting times for web development on the Microsoft stack, but perhaps a little confusing as well. For many years the cycle of moving from one solution and project system to the next hasn't been overly complex. Sure, there have been breaking changes, I've felt those pains myself, but provided the framework you were using continued to live on, there was a reasonable migration path.
Moving to MVC 6 is going to be a big shift for a lot of development teams, but that doesn't mean it needs to be scary, complicated or introduce instability into your project.
Let's Make it Happen
I'm super excited to now be part of the excellent crew at Clear Measure, where this type of attitude seems to be fostered, encouraged and embodied by other members of the team and, more importantly, the management.
We're now undertaking the process of converting from MVC5 => MVC6 with our Bootcamp workshop project and I have the privilege of blogging my experience with it as I go. We're going to keep the project building and operable as we go, such that at an point it can be shipped to production or branched for feature development. We'll be using GitFlow, feature branches, continuous integration and continuous deployment. Our check-ins will be code that builds cleanly with passing tests.
And, for those of you who come join in our our MVC Masters Bootcamp sessions, you'll also get to work on this code base with all the tools, exposure to pair programming, a dedicated product owner and 3 days of intense coding.
Shameless plug: If you want to level up your team of developers, please reach out to Gina Hollis at Clear Measure to plan an on- or off-site event. We promise to melt your minds.
How We're Getting There
Well, to start it off, we're beginning with our initial commit as the MVC 5 project Jeffrey Palermo's been using in the Masters Bootcamp for some time.
The application is hosted on GitHub and you can see the issues that we're identifying and working through. We're doing the whole thing as open source in hopes that other teams can learn from what we learn in the process.
And, as I knock items off the issue list I'll be posting about them here, covering the challenges, pitfalls and wins we encounter along the way. You can bookmark this post for updates in the project. Feel free to ask questions on the issues in the repository, or ping me on Twitter (@CanadianJames).