We have an asp.net mvc4 app integrated with umbraco. It was initially developed as a side-by-side application with umbraco 4.7.2. At that time in global.asax, the web application was descended from HttpApplication. And we defined all our own routes and controllers and actions. We had the UmbraMVCo project that added a route to Umbraco/RenderMvc/{action}/{id}. umbraco was installed off the root of our app but Not configured as a separate app.

After upgrading to 4.11.10 and now 6.0.0, we have removed the UmbraMVCo project and in global.asax, our web application now descends directly from Umbraco.Web.UmbracoApplication. 

We still have all our own routes and controllers and actions. On startup, UmbracoApplication must add a route to umbraco. Because, I can see that there is a route for ~/Umbraco/RenderMvc/{action}/{id} which I don't know what is for. It's not one of our routes. 

We do log into the backoffice via the url, http://xxxxxxxxxxx/umbraco .

But if I attempt to go to http://xxxxxxxxxxx/Umbraco/RenderMvc/ ,

I will trigger a NullReferenceException:

"There is not current PublishedContentRequest, it must be initialized before the RenderRouteHandler executes"

What is that about? Where does that route come from? Is there some way to "get rid" of it?