#Visual studio html inspector full

This is because in Introspection Mode, the Page Inspector starts tracking the mouse hover over each HTML element and then ties it back to the server side page that caused that bit of markup, and then opens the cshtml/vbhtml page and highlights the selection.Ībove we see the ‘Toggle Inspection Mode’ button. Inspection Mode in Page Inspector is a real time saver when debugging rendering and layout issues in applications with complicated page hierarchies. This feature is important for reviewing/debugging portal type applications that may have multiple partial views embedded.

in the image below, we see the current page has been rendered by the partial outputs from Index.cshtml, _Layout.cshtml and _ViewSwitcher.cshtml. The default (Developer tools from IE) are baked in so CSS view, HTML view come by default for application being debugged INSIDE Visual StudioĪ “Files” view indicating the SERVER SIDE files that are used for rendering the current page. This is a one-time (per project) question. On first run, Page Inspector will ask you if it’s okay to add a new config entry. You can select Page Inspector to be your default ‘browser’ of choice so that every time you hit F5, your application executes in it.

#Visual studio html inspector full

The Page Inspector uses the IE browser engine and runs within Visual Studio with full browser functionality - as in JavaScript's, CSS are all applied as if it were a browser. So out of the box you will see IE and the Page Inspector. VS 2012 lists all the browser on your system in the ‘Run’ tool button. Today in this post, we are going to take a look at all the things that Page Inspector can do to speed up debug times for us.įor a lack of better term it’s a new ‘target browser’ for your Web Projects. In our previous article Visual Studio 11 – Awesome New Features for Web Developers, while introducing new features of Visual Studio 2012 (aka VS 11) we had a brief look at a new functionality called Page Inspector.