Great tool for complex routing troubleshooting. The application I support hosts AngularJS and jQuery that works with MVC 5 and a Web API 2 backend. Our route configuration is complicated. This extension has a "URL Mapper" tool that lets you plug in a url and it spits out the matching routes in order of specificity.
Works like a charm... Plus it doesn't have all the limitations of projects like Route Debugger.
One thing I really love is the ability to have all of my MVC routes listed right there within VS, clearly visible and easily mappable. Perhaps I would try to make things a bit faster, if possible, especially with very large projects. Keep up the good work, however! And thank you, guys.
Worst extension I have ever seen. After solution is loaded, all CPU cores are hitting the ceiling and VS becomes unresponsive. It maybe works fine on one simple WebApp, but it's certainly not meant for enterprise level.
Thanks for your comment on our free extension, gotrunx.
We are sorry to hear you experienced a bad performance with this product: it would have been better if you contacted us and opened a support ticket, we would have told you to just disable the code window integration from the options menu to enjoy an overall better performance.
In fact, Routing Assistant includes a code analyzer which scans all of the files for your projects, looking for types and methods which can be decorated as MVC controllers and actions. Depending on the projects size, this can be a lengthy task, which could make your CPU busy for a while (since version 1.8, it happens in different process from the devenv one, so the IDE should not freeze - if it does, please send us your feedback).
That being said, we will try to improve the performances as much as we can in the next versions of the product.
we are sorry to hear you uninstalled Routing Assistant. We believe it offers a great and innovative way for developers to manage their MVC routes and we will do everything we can to improve it.
Your voice and those of many other users have been heard: from now on, you will be able to download Routing Assistant directly from the Visual Studio Gallery with one click and, of course, without any registration process!
The reference to our MVC Extensions is not a requirement but, rather, a way to enable certain "advanced" features in Routing Assistant (like one-click navigation from routes to MVC actions, graphical representation of your declarative routes, etc.) which need MVC Extensions to be installed and referenced from your project(s). The newer version of Routing Assistant states that in a more informative way.
About the dark theme issue: we are sorry for that, unfortunately using themes in Visual Studio is a nightmare (no docs, no guidance, no WPF styles to reuse, nothing). We have fixed some issues with the dark theme and the URL Mapper UI in version 1.7, please let us know if it now looks better.
I have installed this extension on VS 2013 update 3 machine.But it gives below exception when I opened the "Routing Explorer".please advice me ? Thanks in advance.
Exception details, when I click my MVC 4 web project :
System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: This method cannot be called during the application's pre-start initialization phase. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
System.InvalidOperationException: This method cannot be called during the application's pre-start initialization phase.
at SyncInvokeInitApplication(Object , Object , Object )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object inputs, Object& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).
I can't see the details I would look for in the exception log but I suspect this has something to do with some pre-start blocks of code in your project (Application_Start() in your global.asax may be one of them), which are perhaps referring to the current HttpContext.
While this may work in your typical usage scenario, with Routing Assistant pre-start blocks of code are *not* called in the context of an HTTP invocation as it tries to avoid calling specific functionalities of your code, which in turn may bring unexpected consequences. This holds true in other optimization scenarios, like ASP.NET pre-warming, so you may want to re-arrange your code to make it working in these scenarios too.
Hope this helps!
we are actively working on the help material for Routing Assistant in these days. Before being a standalone extension it was part of our MVC Extensions product, so you may want to find some documentation on our website at:
That being said, is there anything specific you would like to see included in the help for Routing Assistant?
Thanks for your feedback!