Visual Studio output window is not displaying mess

问题:

I am using Visual Studio 2010 Professional in trial mode... and suddenly the Output window won't show my Debug.Write() stuff. It had been showing it for the past month.

I have been using the 2010 version for 30 days (after upgrading from Visual Studio 2003) in trial mode. I just renewed the trial for the extra 60 days, and the "About Visual Studio" window says I still have 59 days left.

I have verified that the application is running properly, without errors. When I purposely generate an error, the Output Window properly shows the error and the stack trace I've already checked my Build>Configuration... it's in "Debug" mode, not "Release". The Debug.Write() text is not going to the Immediate window, either.

One other point, I tried running the same application in the Visual Studio 2010 Express Edition, and it complained that it could not debug the specified code, though it did properly build it so that it would run in the build. Could Visual Studio 2010 Express have modified something in my project files to disable the debugging output? I looked, but I really don't know what to look for.

回答1:

Same symptoms for me, different solution:

1. Tools -> Options -> Debugging -> General
2. Uncheck "Redirect all Output Window text to the Immediate Window"

After I did that, debug.print() went to the Output Window like it used to.

Weird that I never checked that option to begin with. Something I did must have caused the setting to change. No idea.

回答2:

There could be another reason the debug information is not showing in the Output window or the Immediate window. If your config file removes the default listener the debug information will not show. Comment out the remove default in the listeners section in your app.config file:

<trace autoflush="true" indentsize="4">
  <listeners>
    <!--<remove name="Default" />-->
  </listeners>
</trace>

回答3:

Please take a look at this other question, which presents several possible reasons for your issue: Where does System.Diagnostics.Debug.Write output appear?

I would start by checking the DEBUG flag.