This blog post has a small correlation to this thread: http://weblogs.asp.net/pwilson/archive/2005/08/21/423209.aspx
The 10th poster makes a brief comment on how the described behavior is already present in the 1.x Framework to some extent. --- "Michael S. Collier" <[EMAIL PROTECTED]> wrote: > I was able to take the FastDbAppender and modify the schema to match > my > table. When I used that, it seemed to fix the SqlException I > mentioned > originally. However, the log messages were still being rolled back. > I > understand that the COM+ transaction was responsible for the roll > back. > What I don't understand yet is why the AdoNetAppender generates that > SqlException, and the FastDbAppender does not. I'll try to look into > this > more. > > Also, I wrote a version of FastDbAppender that derives from > ServicedComponent. I marked this class with the > [Transaction(TransactionOption.NotSupported)] attribute. This seems > to work > as expected. Meaning, log messages generated by this appender > implementation are not part of the COM+ transaction, and thus not > being > rolled back. > > So far this is working in my sample app. I'll move it to my real app > shortly. > > > Do you think the version of FastDbAppender that derives from > ServicedComponent would be something that the Log4Net community as a > whole > would be interested in? > > > Thanks, > Mike
