Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Debug.WriteLine

Debug.WriteLine

Scheduled Pinned Locked Moved C#
comdebuggingquestion
7 Posts 4 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Ray Cassick
    wrote on last edited by
    #1

    Ok, I have just about had enough... Two systems, one laptop one desktop. Built the same small test app on each one. Just a button that when clicked writes the following: Debug.WriteLine("Test"); The laptop writes the 'Test' out tothe debug window just fine... the desktop doe snot. Ready to really throw a fit here... Any ideas before I toss things out the window? Aaaaaaaaaaaaaaaaaaa


    LinkedIn[^] | Blog[^] | Twitter[^]

    L A 2 Replies Last reply
    0
    • R Ray Cassick

      Ok, I have just about had enough... Two systems, one laptop one desktop. Built the same small test app on each one. Just a button that when clicked writes the following: Debug.WriteLine("Test"); The laptop writes the 'Test' out tothe debug window just fine... the desktop doe snot. Ready to really throw a fit here... Any ideas before I toss things out the window? Aaaaaaaaaaaaaaaaaaa


      LinkedIn[^] | Blog[^] | Twitter[^]

      L Offline
      L Offline
      Luc Pattyn
      wrote on last edited by
      #2

      Hi Ray, with the risk to state the obvious: the Debug class only works in a debug build. Check your "Configuration Manager". And check your project properties: in the Build pane, there may be a checkbox "define DEBUG constant" which should be checked. :)

      Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum

      Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

      R 1 Reply Last reply
      0
      • L Luc Pattyn

        Hi Ray, with the risk to state the obvious: the Debug class only works in a debug build. Check your "Configuration Manager". And check your project properties: in the Build pane, there may be a checkbox "define DEBUG constant" which should be checked. :)

        Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum

        Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

        R Offline
        R Offline
        Ray Cassick
        wrote on last edited by
        #3

        Looks good to me... I even changed my setting over to release, ran it and then went back to debug and reran it thinking maybe there was a corrupted configuration or something... No luck...


        LinkedIn[^] | Blog[^] | Twitter[^]

        L 1 Reply Last reply
        0
        • R Ray Cassick

          Looks good to me... I even changed my setting over to release, ran it and then went back to debug and reran it thinking maybe there was a corrupted configuration or something... No luck...


          LinkedIn[^] | Blog[^] | Twitter[^]

          L Offline
          L Offline
          Luc Pattyn
          wrote on last edited by
          #4

          You could replace Debug.WriteLine by Console.WriteLine just to test the statement is reached... :)

          Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum

          Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

          R 1 Reply Last reply
          0
          • L Luc Pattyn

            You could replace Debug.WriteLine by Console.WriteLine just to test the statement is reached... :)

            Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum

            Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

            R Offline
            R Offline
            Ray Cassick
            wrote on last edited by
            #5

            Decided to just bite the bullet and use the 'Reset all settings' option in the 'Import and Export Settings Wizard'. Seems to have resolved the issue. I now have my stuff back written to the Output window now...


            LinkedIn[^] | Blog[^] | Twitter[^]

            P 1 Reply Last reply
            0
            • R Ray Cassick

              Decided to just bite the bullet and use the 'Reset all settings' option in the 'Import and Export Settings Wizard'. Seems to have resolved the issue. I now have my stuff back written to the Output window now...


              LinkedIn[^] | Blog[^] | Twitter[^]

              P Offline
              P Offline
              Pravin Patil Mumbai
              wrote on last edited by
              #6

              Congrats Ray...

              1 Reply Last reply
              0
              • R Ray Cassick

                Ok, I have just about had enough... Two systems, one laptop one desktop. Built the same small test app on each one. Just a button that when clicked writes the following: Debug.WriteLine("Test"); The laptop writes the 'Test' out tothe debug window just fine... the desktop doe snot. Ready to really throw a fit here... Any ideas before I toss things out the window? Aaaaaaaaaaaaaaaaaaa


                LinkedIn[^] | Blog[^] | Twitter[^]

                A Offline
                A Offline
                Abhinav S
                wrote on last edited by
                #7

                Make sure the DefaultTracerListener is set to the debug window on the desktop as well as the laptop. See http://msdn.microsoft.com/en-us/library/system.diagnostics.defaulttracelistener.aspx[^] - this kind of explains it.

                The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it. My latest tip/trick

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • World
                • Users
                • Groups