You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
As soon as I install the Glimpse.WebForms package, it starts dumping the ASP traces to the page. (And yes, my project does combine both aspx web forms and MVC routed razor pages with EF6. Am converting it to mvc)
Is this a user error, or does Glimpse always dump the classic ASP Trace to the output buffer when the WebForms package is installed?
Additionally, if you remove the WebForms package, the asptrace still dumps to the page.
You have to completely remove Glimpse, and reinstall it, to fix the issue.
The text was updated successfully, but these errors were encountered:
ensemblebd
changed the title
Glimpse dumping __asptrace (asp.net trace output) twice
Glimpse dumping __asptrace (asp.net trace output) with WebForms package
Feb 14, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Enabled modules:
As soon as I install the Glimpse.WebForms package, it starts dumping the ASP traces to the page.
(And yes, my project does combine both aspx web forms and MVC routed razor pages with EF6. Am converting it to mvc)
Attempts to resolve..
I've ensured that in my web.config:
And verified that no aspx pages utilize the
Trace=
property for theControl
.Have even forced it at the Base-class for
System.Web.UI.Page
, aka:And yet, there it is on the page output.
Is this a user error, or does Glimpse always dump the classic ASP Trace to the output buffer when the WebForms package is installed?
Additionally, if you remove the WebForms package, the asptrace still dumps to the page.
You have to completely remove Glimpse, and reinstall it, to fix the issue.
The text was updated successfully, but these errors were encountered: