Open richardjharding opened 11 years ago
Good find, I think with the new routing functionality this may not be as much of an issue
On Monday, April 15, 2013, gaspode44 wrote:
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
— Reply to this email directly or view it on GitHubhttps://github.com/erichexter/twitter.bootstrap.mvc/issues/90 .
Eric Hexter
blog | http://Hex.LosTechies.com info | http://www.linkedin.com/in/erichexter
Confirmed this issue.
@erichexter Why do you think this won't be an issue in the new (and highly anticipated :smile:) 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