Ok, so it is RouteConfig.cs and not RouterConfig.cs.
Though, I wonder about this proposed solution from Crystal. Sure, if I have a brand-new project that I created just now, which has RouteConfig.cs - great! But what about other projects, like mine (and I'm sure others), that were created without a RouteConfig.cs? As far as I can see I can't just "Add -> New Item" and choose RouteConfig.cs. Through relentless googling, I can't seem to find anything about the creation of RouteConfig.cs other than the file just appearing when you create a brand new project.
The proposed solution seems narrow in it's scope, and it leaves out alternative project types. I think that Crystal should address this.