Using System.Diagnostics.Debug In An ASP.NET Application

Question

I'm trying to see the output of a foreach loop in my code in the output window in an ASP.NET web app, but I don't get any results even though there is valid data. I've done a fair amount searching using Google with this issue, but nothing I've done works. Here is the code in my ASPX page:

List<MyClass> myClasses = GetMyClasses();
foreach (MyClass myClass in myClasses)
{
    Debug.WriteLine(myClass.SomeProperty);
}

The code is very straight-forward. When I debug this page, myClass.SomeProperty has the value I want, but nothing is getting printed to the output window. What could I be missing? I cannot use a Response.Write because my Response stream is being used to create an Excel file. I also don't want to use Tracing.

Update

I have this in my web.config file:

<system.web>
    ...
    <compilation debug="true" targetFramework="4.0">
    ...
</system.web>

So what was the problem/How did you fix it?

CodesInChaos
– CodesInChaos

2011-06-22 18:08:51 +00:00
Commented Jun 22, 2011 at 18:08 — CodesInChaos
– CodesInChaos, Commented Jun 22, 2011 at 18:08

CodesInChaos · Accepted Answer · 2011-06-13 22:23:12Z

1

(Sorry no full answer, but a bit long for a comment)

There are debug related features. (Related What does the optimize switch do)

Generation of debug Symbols
C# IL optimization
Jitter Optimization
The DEBUG conditional define.

What you need for your problem is the DEBUG conditional. I guess the debug="true" switch affects only the debug symbols but not the conditional.

edit: hmm strange. scottgu states at http://weblogs.asp.net/scottgu/archive/2005/11/06/429723.aspx that debug="true" should affect that conditional.

Note that the value of debug in a web app is driven by the value of the value in your web.config file.

answered Jun 13, 2011 at 22:23

CodesInChaos

109k26 gold badges224 silver badges267 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

chaospixel · Accepted Answer · 2012-04-30 12:22:42Z

1

You are using System.Diagnostics.Trace, rather than the ASP.NET Tracing. To get System.Diagnostics.Trace working within ASP.NET see http://msdn.microsoft.com/en-us/library/b0ectfxd(v=vs.85).aspx.

answered Apr 30, 2012 at 12:22

chaospixel

111 bronze badge

Comments

Wicked Coder · Accepted Answer · 2011-06-13 19:15:37Z

0

I also had a same issue but later found out that Debug.Writeline() didn't work with my unit tests.

answered Jun 13, 2011 at 19:15

Wicked Coder

1,1186 silver badges8 bronze badges

1 Comment

Halcyon Over a year ago

This isn't for a unit test. This is for an ASP.NET web form page. I'm just trying to compare the output for a few foreach loops.

Amasuriel · Accepted Answer · 2011-06-13 19:17:51Z

0

Have you set

<system.web> <compilation debug="true" defaultLanguage="c#" />  </system.web>

in your web.config?

answered Jun 13, 2011 at 19:17

Amasuriel

2,2003 gold badges19 silver badges25 bronze badges

Collectives™ on Stack Overflow

Using System.Diagnostics.Debug In An ASP.NET Application

Update

4 Answers 4

Comments

Comments

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

Update

4 Answers 4

Comments

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related