jwcolby
jwcolby at colbyconsulting.com
Wed Jul 28 00:35:18 CDT 2010
Wow! I must say that NLog is doing everything I need. Well... other than logging to SQL Server which I have not figured out yet. As I wrote in a previous post, I am designing an asynchronous process, consisting of 4 steps where 1) Tables are exported to text files (csv) 2) The files are moved to a vm for processing by a third party application 3) The resulting files (csv) are brought back from the vm 4) The files are imported back in to SQL Server. The objective is to have these 4 steps able to process completely autonomously, completely table driven. I am trying to run each stage on a thread so that each can do it's thing as it sees fit. This brings a large degree of interaction and I need to be able to see where exceptions are thrown, stack traces and all of that. NLog is handling this beautifully. I am not done by any stretch of the imagination but I would be completely unable to figure this out without the exception logging that NLog enables me to do. Very nice stuff. -- John W. Colby www.ColbyConsulting.com