Nicko checked in a MSMQ appender into source control a few days ago.
I'm not familiar with MSMQ in terms of what it guarantees to capture
(is it just a sink?). You could try writing things to there then write
another program to extract the data out and insert it into the
database.
I glanced at NLog's DatabaseAppender.cs code and it looks like when you
set its KeepConnection property to false, calls to DoAppend are not
enclosed in a lock{} block.
Have you looked into the Microsoft Enterprise Library Logging Block?
- Ron
--- Kevin Williams <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > My concern with implementing buffering is that if my appdomain dies
> I
> > will lose the contents of the buffer. I've seen the app domain die
> in
> > testing and can't afford to lose the information in my live
> application.
> > I also have to guarantee that this data has reached the database
> before
> > I move on to actually do something (messaging isn't an option).
>
> Just a thought - I have no idea if it would work for you.
>
> Perhaps you could create a Remoting listener service (as in
> NT/200x/XP
> service) to do the database logging. You could communicate to that
> from
> the RemotingAppender. This could give you an asynchronous messaging
> buffer running in a separate AppDomain and, arguably, a more stable
> environment than ASP.NET.
>
> Cheers,
>
> Kevin
>
