× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Can you give a basic example of doing this? I can see the benefit, but am
having a hard time wrapping my head around when/where you do this and how
it would look in the output.

--
Mike Wills
http://mikewills.me


On Mon, Aug 6, 2012 at 3:58 PM, Walden H. Leverich
<WaldenL@xxxxxxxxxxxxxxx>wrote:

I have great respect for you but this is Boooooring.

Fair enough, but I would say that once you have a system generating
gigabytes of logfiles a day, and have used them to "debug" everything from
real bugs to stupid user errors, you're not likely to want to code a system
w/out logging.

Plus, I find the log entries to be a helpful documentation tool themselves
and the debug() log entries often explain what you're doing so you can
follow the bouncing ball in the log files.

-Walden


--
Walden H Leverich III
Tech Software &
BEC - IRBManager
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com
http://www.IRBManager.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx [mailto:
systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Maurice O'Prey
Sent: Monday, August 06, 2012 4:55 PM
To: '.net use with the System i'
Subject: Re: [SystemiDotNet] IBM i .NET Interface

Walden

I have great respect for you but this is Boooooring.

Maurice :-)

-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Walden H.
Leverich
Sent: 06 August 2012 21:52
To: .net use with the System i
Subject: Re: [SystemiDotNet] IBM i .NET Interface

I have _not_ done an extensive comparison/analysis, but for us the answer
is
yes, I prefer log4net. I think it's a simple but powerful, complete and
capable framework. I love the ability to turn on and off logging by class
(assuming you name your loggers in line w/your classes), the interface is
trivial to use and the output logging options are plentiful, though we only
use rollingFile and syslog in production (and Console in some dev
utilities)
. It's also a logging framework the Java-heads are familiar with if you
need
to integrate with them. And at this point we've got so much code that uses
log4net that I can't imagine changing it :-)

-Walden

--
Walden H Leverich III
Tech Software &
BEC - IRBManager
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com
http://www.IRBManager.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Craig Pelkie
Sent: Monday, August 06, 2012 4:45 PM
To: '.net use with the System i'
Subject: Re: [SystemiDotNet] IBM i .NET Interface

Walden

Just for my edification, would you favor log4net over the Framework tracing
provided in System.Diagnostics, and what are some reasons for the choice.

Thanks
Craig Pelkie

-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Walden H.
Leverich
Sent: Monday, August 06, 2012 1:35 PM
To: .net use with the System i
Subject: Re: [SystemiDotNet] IBM i .NET Interface

I like nice simple code that does simple stuff, well done. (That's a
compliment!) :-)

I would however suggest throwing in log4net code, especially where you've
got the catches. I think of log4net as the joblog, and I can't tell you how
many times it's been handy to have a log of what the code was doing at
runtime.

-Walden

--
Walden H Leverich III
Tech Software &
BEC - IRBManager
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com
http://www.IRBManager.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Mike Wills
Sent: Monday, August 06, 2012 4:14 PM
To: systemidotnet@xxxxxxxxxxxx
Subject: [SystemiDotNet] IBM i .NET Interface

For those that didn't know, I have been working on a .NET interface for
some
of the things that could make life easier when working with IBM i data. The
project is at: https://github.com/MikeWills/IBM-i-.NET-Interface

I am fixing little things as I find issues, but overall this has been
working quite well. Feel free to use it and report issues/submit
fixes/features.

--
Mike Wills
http://mikewills.me
--
This is the .net use with the System i (SystemiDotNet) mailing list To post
a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.
--
This is the .net use with the System i (SystemiDotNet) mailing list To post
a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.

--
This is the .net use with the System i (SystemiDotNet) mailing list To post
a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.
--
This is the .net use with the System i (SystemiDotNet) mailing list To post
a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.

--
This is the .net use with the System i (SystemiDotNet) mailing list
To post a message email: SystemiDotNet@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/systemidotnet.
--
This is the .net use with the System i (SystemiDotNet) mailing list
To post a message email: SystemiDotNet@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/systemidotnet.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.