Debug.Wrile does not appear on the Output Window

  • Thread starter Thread starter =?ISO-8859-1?Q?Bernard_Bour=E9e?=
  • Start date Start date
?

=?ISO-8859-1?Q?Bernard_Bour=E9e?=

In order to trace my job I placed some
Debug.Writeline in my code but they don't appear in the output window!
How to solve it?

Thanks
Bernard
 
Bernard,

Can you show the code?

On MSDN is written how to use it, we cannot change that.
Now you have only told, that it does not appear. By most of us it appears so
you should have done something special.

Cor
 
Are your Debug statements being hit at all ? You can test for this by
setting a breakpoint at the line, and testing if execution stops there.

Regards,

Cerebrus.
 
Cor Ligthert [MVP] a écrit :
Bernard,

Can you show the code?

On MSDN is written how to use it, we cannot change that.
Now you have only told, that it does not appear. By most of us it appears so
you should have done something special.

Cor
Click to expand...
Cor

Of course I can show the code.
I have a small routine in order to trace my code.
Here it is.
It was working fine before but now not.
I have looked at the options but could not find a related item.

Thanks for your help
Bernard

Public Sub PrintLog(ByVal sMsg As String, Optional ByVal sTitre As
String = vbNullString)

Dim fs As New Scripting.FileSystemObject
Dim Stream As Scripting.TextStream
Dim NF As String
NF = NOM_FICHIER_LOG & "_" & Replace(CStr(Today), "/", "_") &
".log"
Stream = fs.OpenTextFile(NF, Scripting.IOMode.ForAppending, True)
Stream.WriteLine(CType(System.DateTime.Now, String))

Stream.WriteLine(sTitre & " : " & sMsg)
Debug.WriteLine(sMsg, sTitre)
Stream.Close()
bLogImprimé = True
End Sub
 
Bernard,

Are you sure that there is not a blank line.

Debug.WriteLine("", vbNullString)
By instance because this is happening

I hope this helps,

Cor
 
Bernard Bourée said:
In order to trace my job I placed some
Debug.Writeline in my code but they don't appear in the output window!
Click to expand...

Are you running the project using the Release or Debug configuration? Maybe
switching to the Debug configuration fixes the problem.
 
Cor Ligthert [MVP] a écrit :
Bernard,

Can you show the code?

On MSDN is written how to use it, we cannot change that.
Now you have only told, that it does not appear. By most of us it appears so
you should have done something special.

Cor
Click to expand...
Cor

No I have a break point on it and have cheked that the string is not empty

Bernard
 
Bernard Bourée said:
Cor Ligthert [MVP] a écrit :
Cor

No I have a break point on it and have cheked that the string is not empty

Bernard
Click to expand...
Just for fun how about trying Debug.Print instead of Debug.Writeline? It
should make no difference but then what you're doing "should" work (assuming
you're in debug mode).
 
Back
Top