VB ASP Trace Outputed to File

[Tris]

I've got a web service running, and i'm trying to build tracing into it that
is outputted to a file. Unfortunately, i can't find a way of enabling TRACE
token, and it just seems to skip over all System.Diagnost ics.Trace lines in
the debugger.
I don't want to use the ASP page trace dump, as it will break my SOAP
interface.

This code is called on my application start event:
Dim lstrFileStream As System.IO.FileS tream
Dim objTraceListene r As System.Diagnost ics.TraceListen er

'Create Stream and Listener
lstrFileStream = New System.IO.FileS tream("C:\Temp\ Tracer.Log",
IO.FileMode.Ope nOrCreate)
objTraceListene r = New
System.Diagnost ics.TextWriterT raceListener(ls trFileStream)
objTraceListene r.TraceOutputOp tions = Diagnostics.Tra ceOptions.Times tamp

'Trace Item
System.Diagnost ics.Trace.Liste ners.Add(objTra ceListener)

This is called at the start of one of the SOAP requests:
System.Diagnost ics.Trace.Write ("Add Account Called.")
System.Diagnost ics.Trace.Flush ()
This generates an empty file, and never writes anything too it.

While i am aware that this style of trace listener may not be ideal, i'd be
happy with it writing anything right now.

Any thoughts?

Cheers Chaps

Tris

[chaz]

you may need this in your web.config

<system.codedom >
<compilers>
<compiler language="c#;cs ;csharp" extension=".cs"
compilerOptions ="/d:TRACE" type="Microsoft .CSharp.CSharpC odeProvider, System,
Version=2.0.350 0.0, Culture=neutral , PublicKeyToken= b77a5c561934e08 9"
warningLevel="1 "/>
<compiler language="VB" extension=".vb"
compilerOptions ="/d:Trace=true" type="Microsoft .VisualBasic.VB CodeProvider,
System, Version=1.0.500 0.0,
Culture=neutral , PublicKeyToken= b77a5c561934e08 9"/>
</compilers>
</system.codedom>
HTHs
"Tris" wrote:

I've got a web service running, and i'm trying to build tracing into it that
is outputted to a file. Unfortunately, i can't find a way of enabling TRACE
token, and it just seems to skip over all System.Diagnost ics.Trace lines in
the debugger.
I don't want to use the ASP page trace dump, as it will break my SOAP
interface.

This code is called on my application start event:
Dim lstrFileStream As System.IO.FileS tream
Dim objTraceListene r As System.Diagnost ics.TraceListen er

'Create Stream and Listener
lstrFileStream = New System.IO.FileS tream("C:\Temp\ Tracer.Log",
IO.FileMode.Ope nOrCreate)
objTraceListene r = New
System.Diagnost ics.TextWriterT raceListener(ls trFileStream)
objTraceListene r.TraceOutputOp tions = Diagnostics.Tra ceOptions.Times tamp

'Trace Item
System.Diagnost ics.Trace.Liste ners.Add(objTra ceListener)

This is called at the start of one of the SOAP requests:
System.Diagnost ics.Trace.Write ("Add Account Called.")
System.Diagnost ics.Trace.Flush ()
This generates an empty file, and never writes anything too it.

While i am aware that this style of trace listener may not be ideal, i'd be
happy with it writing anything right now.

Any thoughts?

Cheers Chaps

Tris