Welcome to the Glimpse Documentation! Here we hope to introduce you to the various tutorials, concepts and APIs you might need when discovering and using Glimpse.

NOTE: Glimpse docs are currently being improved. If you'd like to help out, just edit this page or contribute to our GitHub Wiki

Views Tab

The Views tab displays all calls made to configured View Engine(s) and View(s).

Views Tab

Frequently Asked Questions

  • What are the rows highlighted in yellow and why am I seeing more than one?

    These rows show you successful matches that a View Engine has made. Depending on your scenario you may have many matches as the View Engines may be searched not only to resolve the core view, but also any Partial Views that the page (or Layout / Master Page reference) and/or any DisplayFor/EdititorFor.

  • Why are you showing me non matches (i.e. rows that aren't yellow)?

    As this tab is trying to show you how MVC is searching View Egines within your site, its important to show the non matches that are made. This helps you make decisions as to whether any optimizations can be made in this area (i.e. removing unused View Engines) or where something is not behaving as expected.

Tips and tricks

Unused View Engines

Most people don't know that by default, with the advent of MVC3, there are actually two view engines registered by default (WebFormViewEngine and RazorViewEngine). In most cases, site only actively uses one of these engines.

In the example shown, we can see that the RazorViewEngine is extensively being used, whereas WebFormViewEngine isn't be used. Knowing that in our site we only use RazorViewEngine, we can remove the WebFormViewEngine.

Once done we are actively reducing the number of lookups that are being performed. Here is how you would remove unused view engines:

public class Global : HttpApplication
    public void Application_Start()
        // Clears all previously registered view engines.

        // Registers the Razor view engine.
        ViewEngines.Engines.Add(new RazorViewEngine());