Most likely this is similiar case as it can be with Web API and the call to 'MapHttpAttributeRoutes()'. I've writen a blog post about the Web API and multiple calls to 'MapHttpAttributeRoutes()'. So in your case if the MapMvcAttributeRoutes() is called multiple times the issue comes BUT kind of if you remove your codes call to that it should just start working. If you know how to use ILSpy or a like software you could have a look at the Insights code and then know what it does and what might cause the issue for the routing to not work. So most likely this is related to the order where the call is done to register the attribute based MVC routing.
Thanks Antto, I will look into that.
I'm tying to install our plugin to ensure the functionallity. I have downloaded and installed the latest Foundation version and that works just fine.
I have installed our plugin and the site works is running but when entering the backoffice I get an exception. Neither edit or admin will not load.
The exception is:
I have managed to find out that there is one line of code causing this and that it is this line:
Our plugin is using routing attributes so we need to map these on startup.
Removing that line of code, backoffice works just fine, my menu items are loading correctly but routing does not work of course.
Uninstallning EPiServer.Insight and every thing works just fine.
Does anyone have a clue why MapMvcAttributeRoutes does not work with EPiServer.Insight?