log4net...
-
Has anyone here used it for any projects? Log4net clickety[^] I have been looking it over for a project and am looking for some other impartial views of it.
Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on the wall."
George Carlin wrote: "Don't sweat the petty things, and don't pet the sweaty things."
-
Has anyone here used it for any projects? Log4net clickety[^] I have been looking it over for a project and am looking for some other impartial views of it.
Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on the wall."
George Carlin wrote: "Don't sweat the petty things, and don't pet the sweaty things."
SOme people swear by log4net and NUnit, but I dont even know what purpose they serve :wtf:, maybe one day...:) WebBoxes - Yet another collapsable control, but it relies on a "graphics server" for dynamic pretty rounded corners, cool arrows and unlimited font support.
-
SOme people swear by log4net and NUnit, but I dont even know what purpose they serve :wtf:, maybe one day...:) WebBoxes - Yet another collapsable control, but it relies on a "graphics server" for dynamic pretty rounded corners, cool arrows and unlimited font support.
:-D I've not used NUnit yet, but I do plan on including it with the development of my University degree's final year project (a big distributed commercial web service -- see a post below for a basic overview). Anyway, NUnit is just a way of building automated unit tests, with the aim of producing a suite of tests that you can run to prove that the code does what it's supposed to -- and that anything you add hasn't broken something old. The way I'm looking at including it from the outset (you add attributes 'n stuff :)) is around a kind of one-person eXtreme Programming. By using these tests I can ensure to a certain degree that the code is successful, and should give me some good info to put in the report with regards to testing. The other thing about XP (as far as I've understood it) is that one of the aims is to build elements of a system as quickly as possible, once its functional you move on. So I can do tests for features, once the tests complete ok I can move on ... there isn't a great deal of design involved before the coding. I have to say its quite bureaucratic (including all this NUnit testing support) but I'm hoping it'll be worthwhile in the long-run, and should be a good learning experience. -- Paul "If you can keep your head when all around you have lost theirs, then you probably haven't understood the seriousness of the situation." - David Brent, from "The Office" MS Messenger: paul@oobaloo.co.uk Sonork: 100.22446
-
SOme people swear by log4net and NUnit, but I dont even know what purpose they serve :wtf:, maybe one day...:) WebBoxes - Yet another collapsable control, but it relies on a "graphics server" for dynamic pretty rounded corners, cool arrows and unlimited font support.
Use NUnit (and NAnt which is awesome) for team development: daily builds and automated testing are essential whenever you're working with others on a project. I didn't look into Log4net yet; i think it uses the pattern of Listeners which you can attach to a general logging system; just as you can do with the Trace classes in .NET Gertjan Schuurmans Amsterdam The Netherlands