Hey, I'm the developer of ReactJS.NET. Thanks for trying it out! > Any client-side routes will need to be mirrored on the server if you want isomorphism. This

Hey, I'm the developer of ReactJS.NET. Thanks for trying it out! > Any client-side routes will need to be mirrored on the server if you want isomorphism. This means you're using two routers. A while back I worked on a library called [RouteJs](http://dan.cx/projects/routejs http://dan.cx/projects/routejs) that would expose certain ASP.NET MVC routes to JavaScript. The use case here was to have a way to build URLs client-side rather than hard-coding them (similar to the `Url.Action` helper in Razor) but a similar technique could be used to do client-side routing. That's actually a really good feature request for RouteJs :) > The next issue is that most of the examples out there are simplistic. They will show a simple page with one component embedded that swaps out a part of the view. Yeah, that's true. I have one page using server-side rendering in production, and it's a page on my site/blog: http://dan.cx/socialfeed.htm http://dan.cx/socialfeed.htm. It's also a simple page but I used it for building the original proof-of-concept for server-side rendering. I haven't actually tried using ReactJS.NET to build a single-page app, but I think that would be an interesting use case.