Writing Assertions to a log file?

[Brett Romero]

I'd like to use Debug.Assert() but output to a log file instead of the
popup window. Can some one provide an example of how that is done? Or
will C# only let you use th popup window?

Thanks,
Brett

[Andreas Mueller]

Brett Romero wrote:

I'd like to use Debug.Assert() but output to a log file instead of the
popup window. Can some one provide an example of how that is done? Or
will C# only let you use th popup window?

Thanks,
Brett

http://msdn2.microsoft.com/en-us/library/ty5e4c4h.aspx
http://msdn2.microsoft.com/en-us/library/76dt1k3h.aspx

HTH,
Andy
--
You can email me directly by removing the NOSPAm below
xm**********@gm xNOSPAm.netNOSPAm

[Brett Romero]

Thanks. This gives output similar to:

---- DEBUG ASSERTION FAILED ----
---- Assert Short Message ----
b.Equals(0): False
---- Assert Long Message ----

at Startup.UT() C:\Test\TestCon sole\Main.cs(27 )
at Startup.Main(St ring[] args) C:\Test\TestCon sole\Main.cs(18 )
at AppDomain.nExec uteAssembly(Ass embly assembly, String[] args)
at AppDomain.Execu teAssembly(Stri ng assemblyFile, Evidence
assemblySecurit y, String[] args)
at HostProc.RunUse rsAssembly()
at ThreadHelper.Th readStart_Conte xt(Object state)
at ExecutionContex t.Run(Execution Context executionContex t,
ContextCallback callback, Object state)
at ThreadHelper.Th readStart()

Is there a way to just output just this part:

---- DEBUG ASSERTION FAILED ----
---- Assert Short Message ----
b.Equals(0): False
---- Assert Long Message ----

at Startup.UT() C:\Test\TestCon sole\Main.cs(27 )
at Startup.Main(St ring[] args) C:\Test\TestCon sole\Main.cs(18 )

The other information is useless to me. The message, file, and a line
number with current code and caller is all I need.

Thanks,
Brett

[Andreas Mueller]

Brett Romero wrote:

Thanks. This gives output similar to:

---- DEBUG ASSERTION FAILED ----
---- Assert Short Message ----
b.Equals(0): False
---- Assert Long Message ----

at Startup.UT() C:\Test\TestCon sole\Main.cs(27 )
at Startup.Main(St ring[] args) C:\Test\TestCon sole\Main.cs(18 )
at AppDomain.nExec uteAssembly(Ass embly assembly, String[] args)
at AppDomain.Execu teAssembly(Stri ng assemblyFile, Evidence
assemblySecurit y, String[] args)
at HostProc.RunUse rsAssembly()
at ThreadHelper.Th readStart_Conte xt(Object state)
at ExecutionContex t.Run(Execution Context executionContex t,
ContextCallback callback, Object state)
at ThreadHelper.Th readStart()

Is there a way to just output just this part:

---- DEBUG ASSERTION FAILED ----
---- Assert Short Message ----
b.Equals(0): False
---- Assert Long Message ----

at Startup.UT() C:\Test\TestCon sole\Main.cs(27 )
at Startup.Main(St ring[] args) C:\Test\TestCon sole\Main.cs(18 )

The other information is useless to me. The message, file, and a line
number with current code and caller is all I need.

Thanks,
Brett

Here is some sample code:

using System.Diagnost ics;
using System.IO;

namespace ConsoleApplicat ion
{
public class LogListener : DefaultTraceLis tener
{
public override void Fail(string message, string detailMessage)
{
// needs to pop up UI
if(AssertUiEnab led)
base.Fail(messa ge, detailMessage);

// is a log file configured??
if (LogFileName == null
|| LogFileName == string.Empty)
return;

using (StreamWriter logFile =
new StreamWriter(Lo gFileName, true))
{
StackTrace stack = new StackTrace();
StackFrame[] frames = stack.GetFrames ();

// extract and log what you need....
logFile.WriteLi ne(stack);
}
}
}
class Program
{
static void Main(string[] args)
{
Debug.Assert(fa lse, "BOOM");
}
}
}

By using the following app.config aou can inject your implemetation:

<?xml version="1.0" encoding="utf-8" ?>
<configuratio n>
<system.diagnos tics>
<trace autoflush="true " indentsize="0">
<listeners>
<clear />
<!--Use full qualified type name-->
<add
name="LogListen er"
type="ConsoleAp plication.LogLi stener, ConsoleApplicat ion"
/>
</listeners>
</trace>
<assert assertuienabled ="false" logfilename="c: \log.txt"/>
</system.diagnost ics>
</configuration>

HTH,
Andy
--
You can email me directly by removing the NOSPAm below
xm**********@gm xNOSPAm.netNOSPAm

[Brett Romero]

Thanks. I'm guessing if I want to clear the log file before each
execution of the app, I'll need to add that to the LogListener class?

Brett

[Noah Sham]

....and the link that tells you to override TraceListener.F ail() and other
details is http://msdn2.microsoft.com/en-us/library/ttcc4x86.aspx
"Andreas Mueller" <[e-mail] wrote in message
news:4n******** ****@individual .net...

Brett Romero wrote:

>Thanks. This gives output similar to:

---- DEBUG ASSERTION FAILED ----
---- Assert Short Message ----
b.Equals(0): False
---- Assert Long Message ----

at Startup.UT() C:\Test\TestCon sole\Main.cs(27 )
at Startup.Main(St ring[] args) C:\Test\TestCon sole\Main.cs(18 )
at AppDomain.nExec uteAssembly(Ass embly assembly, String[] args)
at AppDomain.Execu teAssembly(Stri ng assemblyFile, Evidence
assemblySecuri ty, String[] args)
at HostProc.RunUse rsAssembly()
at ThreadHelper.Th readStart_Conte xt(Object state)
at ExecutionContex t.Run(Execution Context executionContex t,
ContextCallbac k callback, Object state)
at ThreadHelper.Th readStart()

Is there a way to just output just this part:

---- DEBUG ASSERTION FAILED ----
---- Assert Short Message ----
b.Equals(0): False
---- Assert Long Message ----

at Startup.UT() C:\Test\TestCon sole\Main.cs(27 )
at Startup.Main(St ring[] args) C:\Test\TestCon sole\Main.cs(18 )

The other information is useless to me. The message, file, and a line
number with current code and caller is all I need.

Thanks,
Brett

Here is some sample code:

using System.Diagnost ics;
using System.IO;

namespace ConsoleApplicat ion
{
public class LogListener : DefaultTraceLis tener
{
public override void Fail(string message, string detailMessage)
{
// needs to pop up UI
if(AssertUiEnab led)
base.Fail(messa ge, detailMessage);

// is a log file configured??
if (LogFileName == null
|| LogFileName == string.Empty)
return;

using (StreamWriter logFile =
new StreamWriter(Lo gFileName, true))
{
StackTrace stack = new StackTrace();
StackFrame[] frames = stack.GetFrames ();

// extract and log what you need....
logFile.WriteLi ne(stack);
}
}
}
class Program
{
static void Main(string[] args)
{
Debug.Assert(fa lse, "BOOM");
}
}
}

By using the following app.config aou can inject your implemetation:

<?xml version="1.0" encoding="utf-8" ?>
<configuratio n>
<system.diagnos tics>
<trace autoflush="true " indentsize="0">
<listeners>
<clear />
<!--Use full qualified type name-->
<add
name="LogListen er"
type="ConsoleAp plication.LogLi stener, ConsoleApplicat ion"
/>
</listeners>
</trace>
<assert assertuienabled ="false" logfilename="c: \log.txt"/>
</system.diagnost ics>
</configuration>

HTH,
Andy
--
You can email me directly by removing the NOSPAm below
xm**********@gm xNOSPAm.netNOSPAm

[Andreas Mueller]

Brett Romero wrote:

Thanks. I'm guessing if I want to clear the log file before each
execution of the app, I'll need to add that to the LogListener class?

Brett

Yeah, that should be a good place:

using System.Diagnost ics;
using System.IO;

namespace ConsoleApplicat ion
{
public class LogListener : DefaultTraceLis tener
{
private static bool initialized = false;
public override void Fail(string message, string detailMessage)
{
if(!initialized )
{
if(File.Exists( LogFileName))
File.Delete(Log FileName);
initialized = true;
}
// needs to pop up UI
if(AssertUiEnab led)
base.Fail(messa ge, detailMessage);

// is a log file configured??
if (LogFileName == null
|| LogFileName == string.Empty)
return;

using (StreamWriter logFile =
new StreamWriter(Lo gFileName, true))
{
StackTrace stack = new StackTrace();
StackFrame[] frames = stack.GetFrames ();

// extract and log what you need....
logFile.WriteLi ne(stack);
}
}
}
class Program
{
static void Main(string[] args)
{
Debug.Assert(fa lse, "BOOM");
Debug.Assert(fa lse, "BOOM");
}
}
}
HTH,
Andy
--
You can email me directly by removing the NOSPAm below
xm**********@gm xNOSPAm.netNOSPAm

[Brett Romero]

Andreas, what is needed to actually use the custom listener class?
When I call Debug.Assert(), it isn't using the custom listener. I say
that because the log is not cleared and break points in the class
aren't hit.

Thanks,
Brett

[Brett Romero]

Sorry, I didn't have the listeners section configured in the config
file.

Brett