Skip to content
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.

Glimpse dumping __asptrace (asp.net trace output) with WebForms package #1012

Open
ensemblebd opened this issue Feb 14, 2018 · 0 comments
Open

Comments

@ensemblebd
Copy link

ensemblebd commented Feb 14, 2018

Enabled modules:

  • Glimpse v1.8.6
  • Glimpse.AspNet v1.9.2
  • Glimpse.Mvc5 v1.5.3
  • Glimpse.Ado v1.7.3
  • Glimpse.EF6 v1.6.5
  • Glimpse.WebForms v1.1.1

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:

<system.web>
    <trace enabled="false" />
</system.web>

And verified that no aspx pages utilize the Trace= property for the Control.
Have even forced it at the Base-class for System.Web.UI.Page , aka:

			Page.Trace.IsEnabled = false;
			Trace.IsEnabled = false;

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.

@ensemblebd 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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant