-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Glimpse nuget package breaks navigation extension #90
Comments
Good find, I think with the new routing functionality this may not be as On Monday, April 15, 2013, gaspode44 wrote:
Eric Hexter blog | http://Hex.LosTechies.com |
Confirmed this issue. |
@erichexter Why do you think this won't be an issue in the new (and highly anticipated 😄) navigation routes? |
Confirmed this issue and also ditto @serra in asking why it won't be an issue in the new navigation routes? |
Confirmed the issue. |
Fixed this issue by editing my glimpse settings in my web.config <glimpse defaultRuntimePolicy="On" endpointBaseUri="~/Glimpse.axd">
<inspectors>
<ignoredTypes>
<add type="Glimpse.AspNet.Inspector.RoutesInspector, Glimpse.AspNet" />
</ignoredTypes>
</inspectors>
<tabs>
<ignoredTypes>
<add type="Glimpse.AspNet.Tab.Routes, Glimpse.AspNet" />
</ignoredTypes>
</tabs>
<!-- Runtime Policy Management
<runtimePolicies>
<ignoredTypes>
<add type="{Namespace.Type, AssemblyName}" />
</ignoredTypes>
</runtimePolicies>
-->
</glimpse> |
To be fair not sure if this is an issue for this project or Glimps but as Glimpse is a popular add on to mvc thought it was worth raising
Adding in Glimps causes the GetRoutesForCurrentRequest method to fail as all routes are returned as Glimpse route proxy types and so the query for objects of type NamedRoute returns zero results
The text was updated successfully, but these errors were encountered: