no output visible from debug.print(...)

Hi
I create a simple Windwos Form Application, place one button on the main form which executes debug.print("hello")

Pressing the button while running the application in IDE generates no output in the Output window. (neither 'Show output from: Debug' nor 'Show output from: Build'


Debug is the active configuration and 'Program Output' and 'Exception Messages' are enabled to show in the Output window.

My IDE is:
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: IDE Standard

Does anybody know how to resolve my problem

Thanks
Reto



Answer this question

no output visible from debug.print(...)

  • Jombi

    The Express edition does have the 'Immidiate Window' on the menu exactly where Johan S. States it to be.



  • lray801

    Are you using the Visual Basic settings If so, the output will end up in the immediate window (Debug->Windows->Immediate)

    Best regards,
    Johan Stenberg



  • The_Real_MBu

    Did you include a handle in your button's click event to point back to the click event

    mac318


  • kehoe


    <Ctrl><G> opens the "goto line number" dialog in my IDE.

    Pressing <Ctrl><Alt><I> opens the Immediate Window. Then I can dock it to my views.

    My primary porblem is solved so far, but it leads me to the unpleasant feeling, there's much more VS2005 can do, but I can't use it because it's invisible for me ;-).

    I still miss several entries in Debug/Windows/......
    There are only 5 visible in my IDE while running in debug mode (-> last post). My colleague's IDE has many more. (e.g. Output, Script Explorer, Autos, Immediate, Modules, Processes, Memory, Disassembly, Registers). If I use the <Ctrl><Alt><.....> keys I get the functionality.

    What hides those functions

    Reto


  • Chris Berg

    That's it mac318.
    I set the values to 'Visual Basic Development Settings'.


    What a wonderful world...

    Many thanks to you and all who did bother to solve my problems.

    Reto




  • JFlan

    Hi Johan

    There is no Debug/Windows/Immediate in my IDE.

    In Debug/Windows/ there are only 5 entries:
    Breakpoints, Watch, Locals, Call Stack, Threads (available while debugging)

    Now I noticed the Option 'Redirect all Output Window text to the Immediate Window' in Tools/Options/Debugging/General.

    Changing this brought back the output to the Output Window so far.
    Thanks for your hint.
    But where is the mentioned Immediate Window








  • Stephen Witter

    Yes,
    Private Sub Button1_Click_1(ByVal sender As System.Object, ByVal e As System.EventArgs) _
    Handles Button1.Click
    Debug.Print("hello")
    MsgBox("hello again")
    End Sub

    everything else in the Sub works fine , except that I cannot find the "hello" message.

    Reto


  • gerbilferrit

    Press <Ctrl><G> to bring up the Immediate Window while you are in the code window after you run the above procedure.  That works for me.

     

    mac318

     


  • jpatrick62

    In case you have the exxpress edition of VB 2005 ( I can't tell from the description you have included), then I believe the express edition does not contain an Immediate window "feature". Sorry if this does not apply to your situation.
  • Eamonn Turley

    Found a solution which is to reset settings by going to the Tools -> Import and Export Settings... -> Reset All Settings wizard.

    Your current keyboard is mapped to vs6 and it needs mapping to 8.

    mac318


  • onlyican

    I have both vs2005 Express and Professional. Both of these go to the immediate window when I press <Ctrl><G>. Is there any chance that your keyboard has been remapped

    For the second part of your previous message: Select "Tools", "Customize", "Commands." You can add any of the commands to your toolbar(s) by using drag and drop thus making them available in the code window.

    mac318

    p.s. Stay strong my friend. There's always a solution. I'm going to do a little research on your <Ctrl><G> problem. It could be something as simple as a Check box at the Solution or Project level causing havoc with your mind.


  • no output visible from debug.print(...)