c#,asp.net,debugging,webforms,glimpse
You need to install the Glimpse.Ado NuGet package as well as it contains the necessary SQL related hooks. If you are using Entity Framework then you can install one of the following NuGet packages Glimpse.EF43 NuGet package Glimpse.EF5 NuGet package Glimpse.EF6 NuGet package The Glimpse.EFx NuGet packages will automatically install...
It sounds like your policy is either returning RuntimePolicy.Off or RuntimePolicy.On. What you should do instead is not turn Glimpse off, but return RuntimePolicy.PersistResults so that Glimpse will capture the information about the request, but not inject HUD or the full client. You can see more about the various levels...
Fixed in https://github.com/Glimpse/Glimpse/issues/812 Available in next release...
This should work for what you want - How to display timeline information for routines used by controllers in glimpse/Asp.NET MVC. There is also this - http://thenextdoorgeek.com/post/Extending-Glimpse-for-ASPNET-to-include-custom-Timeline-messages.
c#,.net,async-await,ado,glimpse
This: var result = cmd.ExecuteReaderAsync().Result; Is causing your code to deadlock. I'm assuming you're running an app which passes around a synchronization context (UI, ASP.NET, Universal App or such). This is why you shouldn't block on async code To get around this, you'll have to make your method async Task...
Ok, the reason why clicking on the "Turn Glimpse Off" button has no effect is because the ControlCookiePolicy is disabled in the config, hence clicking that button will have no effect. So you need to remove that entry from the config to make that work again: <add type="Glimpse.Core.Policy.ControlCookiePolicy, Glimpse.Core" />...
Figured this out- My web.config file had <appSettings> <add key="Glimpse:DisableAsyncSupport" value="true"/> </appSettings> Removing this value or setting it to false resolves the issue....
asp.net-mvc-4,azure,azure-web-roles,glimpse,.net-4.5
Found my solution on the troubleshooting page of Glimpse. In short, url compression was applied so had to disable this in the web.config: <system.webServer> <urlCompression doDynamicCompression="true" dynamicCompressionBeforeCache="false" /> </system.webServer> ...
asp.net-mvc,asp.net-mvc-3,asp.net-mvc-4,asp.net-mvc-5,glimpse
Unfortunately that trigger is focused on system web's tracing and not Glimpse. We could change things to adhere to that config point, but it doesn't currently. Hence the following is what you want in you web.config: <glimpse defaultRuntimePolicy="On" endpointBaseUri="~/Glimpse.axd"> <inspectors> <ignoredTypes> <add type="Glimpse.Core.Inspector.TraceInspector, Glimpse.Core" /> </ignoredTypes> </inspectors> </glimpse> And if...
You need to also install Glimpse.WebForms. The Glimpse.AspNet package contains a few tabs and useful abstractions across both MVC and WebForms, but nothing specific to the "Host" section of HUD....
c#,asp.net,asp.net-mvc,glimpse
Glimpse is a web debugging and diagnostics tool used to gain a better understanding of whats happening inside of your ASP.NET 4.0 application As you hover over each segment, it pops up with lots of details about the HTTP request, AJAX requests, deep inspection database interactions, and lots more. You...
Let me first start explaining what the following means a read only capacity (meaning Glimpse will collect the information but they can't view it) Glimpse has a bunch of IRuntimePolicy implementations that come out-of-the-box and there are many more, third party or custom made. Those IRuntimePolicy implementations determine how far...
Well, I figured it out. But first, take a look at the exact usage scenario that would need to be in place for the problem to occur. Usage Scenario The problem only occurs if you: a. Have lazy loading enabled for the context. b. Pass your EF model to the...
In case of 1 the GlimpseRuntime will detect that it should not trace actions going on during any of the requests. This value is one of the Glimpse Runtime Policy values of which Off is the most restricted one. Keep in mind that there will still be a little bit...
asp.net,asp.net-mvc,httphandler,glimpse
I think you more or less already provided the answer to your question by stating If it only needed to support ASP.Net MVC, would it make more sense to just use an MVC or Web API controller From that point of view it seems logical to use an IHttpHandler approach...
Unfortunately, Glimpse, as of version 1.8.6 (of the core package) does not support this. Technically your could easily write an extension that does this, but its such a common request that we are adding it in to the next release. It's actually already documented at http://getglimpse.com/Docs/Timeline-Tab. You could also just...
Great question... The Client time is the difference between loadEventEnd and responseEnd (you can see the relevant code here). In English terms this everything that happens from the time the browser receives last byte from the server (for the main document) to when the load event for the current document...
The one on the right most side (i.e. 200.07ms and 211.85ms) are how long the connection was opened for. The one next to the record count, is how long the command took to execute.
The reason is that even when you disable Glimpse completely through the web.config, which makes sure Glimpse is not collecting any information during request processing, that there are still assemblies, like Glimpse.Ado and Glimpse.EF*, that have a PreApplicationStartMethod attribute defined, which means that some hooks are being put in place,...
asp.net-mvc,entity-framework,glimpse
Glimpse has been built around the philosophy to have it run with the least amount of additional config or code for users to add or write themselves. Granted this comes with the additional drawback that if you want to disable it completely, that changes from your side will be required...
asp.net-mvc-5,sitecore,glimpse,sitecore7.2
The solution mentioned in this post on the Glimpse issue tracker solved the problem. Sitecore does it's own HttpModule stuff which seems to cause issues. In order to fix this, you need to move the Glimpse HttpModule definition before the Sitecore modules in the Web.config. ...
What you are describing is actually normal behavior and has everything to do with the order in which routes are being registered. Let me explain it, based on a green field project as the one you created to pinpoint the problem. When you create a new MVC project and you...
c#,asp.net,asp.net-mvc,asp.net-mvc-5,glimpse
If the glimpse.axd is returning a 404 then this means the Glimpse resource handler is not registered. If the web.config content you show above is not trimmed to much, then it is normal that Glimpse won't do much as the Glimpse HttpModule and the Glimpse HttpHandler are not registered in...
The solution I chose was to override the SqlServerOrmLiteDialectProvider.CreateDbConnection()similar to this solution. var dbFactory = new OrmLiteConnectionFactory( "<connection string>", SqlServerWithGlimpseDialectProvider.Instance); public class SqlServerWithGlimpseDialectProvider : SqlServerOrmLiteDialectProvider { public new static SqlServerWithGlimpseDialectProvider Instance = new SqlServerWithGlimpseDialectProvider(); public override IDbConnection CreateConnection(string connectionString, Dictionary<string, string>...
javascript,ajax,asp.net-mvc,glimpse
You have gotten a fairly large amount of the way towards your goal. Unfortunately though there isn't really a way of getting data from a tab outside of a request. That said, there is a "Glimpse" way of getting data from the server. This is small semantic difference, but it...
asp.net,asp.net-mvc,azure,azure-web-sites,glimpse
This is EasyAuthModule is actually a Microsoft library. The Azure support informed me, they had just moved to a native library EasyAuthModule. There seems to be a compatibility issue with Glimpse though. After removing any Glimpse reference from my web.config, it's now working fine! The Azure support told me they...