home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Suggestion
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Anonymous" data-source="post: 3236"><p>hi,</p><p></p><p>Some assemblies need the guilib only for the log class. The log class is not GUI. Why not make a single assembly only for logging. </p><p></p><p>Extend the log class with Trace.xxx to redirect the log output at runtime to windows debugout kernel. So every body can see debug output at runtime (with sys internal dbgview.exe). I always use only dbgview.exe.</p><p>You can filter the output and choose the color for a line ...</p><p></p><p>elli</p></blockquote><p></p>
[QUOTE="Anonymous, post: 3236"] hi, Some assemblies need the guilib only for the log class. The log class is not GUI. Why not make a single assembly only for logging. Extend the log class with Trace.xxx to redirect the log output at runtime to windows debugout kernel. So every body can see debug output at runtime (with sys internal dbgview.exe). I always use only dbgview.exe. You can filter the output and choose the color for a line ... elli [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Suggestion
Contact us
RSS
Top
Bottom