Error logging


Author
Message
Douglas Earl
Douglas Earl
Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)
Group: Forum Members
Posts: 15, Visits: 1

Ocassionally I'll see a Nevron message in the VS output window when debugging.  For example, here's one I get when I try to load a 2012 file using Nevron 2011: Failed to load from file. Exception was: The element or one of its descendants has an invalid unique id.

My question is, do these types of messages get saved to a log file anywhere? Or is there some utility that our customer could run that would intercept these messages? Thanks,

Doug


Douglas Earl
Douglas Earl
Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)
Group: Forum Members
Posts: 15, Visits: 1

Could one of the engineers take a quick look and tell me what technique is used to perform logging?  Is it just Console.WriteLine or something more sophisticated?

Specifically, what I'm trying to find out is that we have some customers who can't load an .nlx file during initialization of our product.  I'd like to find out if there is some way to see what Nevron is logging as to the reason.  Very similary to the example shown in my original post, no execption is thrown, so I'm hoping there is something logged that I can look at.

Thanks.


Nevron Support
Nevron Support
Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)Supreme Being (4.5K reputation)
Group: Administrators
Posts: 3.1K, Visits: 4.2K

Hi,

Generally the diagram traces all caught exceptions with the standard for .NET Trace.WriteLine method. You can easily intercept the trace like that:

....
    Trace.Listeners.Add(new MyTraceListener());
....

public class MyTraceListener : TraceListener
{
    public override void Write(object o)
    {
        base.Write(o);
    }

    public override void WriteLine(string message)
    {
        Console.WriteLine("WriteLine: " + message);
    }

    public override void Write(string message)
    {
        Console.WriteLine("Write: " + message);
    }
}



Best Regards,
Nevron Support Team


Douglas Earl
Douglas Earl
Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)Junior Member (15 reputation)
Group: Forum Members
Posts: 15, Visits: 1
Thanks. In case anyone else is interested, I found DebugView from SysInternals, which captured a Nevron Trace message in my initial test:
http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search