I just installed Glimpse.Mvc3 from NuGet. The package enabled trace and glimpse in my web.config. I can successfully get to localhost/.../Glimpse/Config (so no 404) and it reports that my IP is 127.0.0.1 and matches the allowed list. Clicking the On button shows my glimpseState = On (and I verified that the cookie is set). But when I go back and refresh my project, I see nothing new. Is there something else I need to be doing?
My end goal here is to figure out why my site is a little sluggish, taking at least a full second every page. In webforms days, I would have otherwise just set Page.Trace=True and gotten a nice timestamped log, but such is not an option in MVC. Glimpse seems like it will fill that role and more.
Edit: I just opened my javascript error console and see that it is having issues loading localhost/.../Glimpse/glimpseClient.js and when I try to go there directly, I instantly get a very broken link. By that I mean it's not a 404, it acts like the server doesn't exist at all (a browser-specific page). Swapping "glimpseClient.js" for "Config" brings up the proper page, so the server address seems fine.
Edit2: I see an open issue on the project's github that sounds similar. Looking at the HTML source of my site, I see a bunch of glimpse code added at the bottom. glimpsePath is properly set to my virtual directory. My web.config already had runAllManagedModulesForAllRequests="true" set.
I'm one of the developers on glimpse and this issue is known and has just been resolved... please see http://blog.getglimpse.com/2011/06/21/404-errors-fixed-goodbye-glimpseconfig-hello-glimpse-axd/.
This is a known issue for a small percentage of users and if you read the post it goes pretty indepth about how and why this occurred. The fix will be in release 0.83+ which should be coming out within the week.
Sorry about any inconvenience.