[jira] [Updated] (LOG4NET-119) XML configuration: update="Merge" does not work as expected

[ https://issues.apache.org/jira/browse/LOG4NET-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-119: --- Fix Version/s: 1.2 Maintenance Release > XML configuration: update="Merge" does not work as

[jira] [Updated] (LOG4NET-117) Migrate web content generation of Maven 2.0

[ https://issues.apache.org/jira/browse/LOG4NET-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-117: --- Fix Version/s: 1.2.11 Assignee: Stefan Bodewig I was going to look into how the cur

[jira] [Updated] (LOG4NET-118) RollingFileAppender: RollingStyle=Size with StaticLogFileName=false does not work

[ https://issues.apache.org/jira/browse/LOG4NET-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-118: --- Fix Version/s: 1.2.11 > RollingFileAppender: RollingStyle=Size with StaticLogFileName=false

[jira] [Updated] (LOG4NET-105) [PATCH] logical thread context

[ https://issues.apache.org/jira/browse/LOG4NET-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-105: --- Fix Version/s: 1.2 Maintenance Release > [PATCH] logical thread context > -

[jira] [Resolved] (LOG4NET-114) Unit tests only support .NET 1.0

[ https://issues.apache.org/jira/browse/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved LOG4NET-114. Resolution: Fixed At least the original issue has long been resolved, tests can be run for

[jira] [Updated] (LOG4NET-103) RollingFileAppenders that log to a network share from a web application fail to resume logging in the event the network share is disconnected/reconnected/failsover

[ https://issues.apache.org/jira/browse/LOG4NET-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-103: --- Fix Version/s: 1.2 Maintenance Release > RollingFileAppenders that log to a network share fr

[jira] [Updated] (LOG4NET-102) AdoNetAppender issue using System.Data.OracleClient

[ https://issues.apache.org/jira/browse/LOG4NET-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-102: --- Fix Version/s: 1.2 Maintenance Release > AdoNetAppender issue using System.Data.OracleClient

[jira] [Updated] (LOG4NET-82) RollingFileAppender: Cannot RollFile ... Source does not exist

[ https://issues.apache.org/jira/browse/LOG4NET-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-82: -- Fix Version/s: 1.2.11 > RollingFileAppender: Cannot RollFile ... Source does not exist > -

[jira] [Updated] (LOG4NET-83) Allow flushing into file every X milliseconds

[ https://issues.apache.org/jira/browse/LOG4NET-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-83: -- Fix Version/s: 1.2 Maintenance Release > Allow flushing into file every X milliseconds > --

[jira] [Updated] (LOG4NET-80) Allow LogitcalThreadContextProperties to be stored in HttpContext.Items instead of CallContext

[ https://issues.apache.org/jira/browse/LOG4NET-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-80: -- Due Date: 13/Jul/05 (was: 13/Jul/05) Fix Version/s: 1.2 Maintenance Release > Allow L

[jira] [Updated] (LOG4NET-76) TextWriterAdapter is not thread safe

[ https://issues.apache.org/jira/browse/LOG4NET-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-76: -- Fix Version/s: 1.2.11 > TextWriterAdapter is not thread safe >

[jira] [Updated] (LOG4NET-71) Reorganise source repository to support multiple src projects

[ https://issues.apache.org/jira/browse/LOG4NET-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-71: -- Fix Version/s: 2.0 I agree reshuffling the source try may be a good idea but prefer to do that

[jira] [Updated] (LOG4NET-68) EntLib application block

[ https://issues.apache.org/jira/browse/LOG4NET-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-68: -- Fix Version/s: 1.2 Maintenance Release > EntLib application block > >

[jira] [Updated] (LOG4NET-47) Add AsyncForwardingAppender

[ https://issues.apache.org/jira/browse/LOG4NET-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-47: -- Fix Version/s: 1.2 Maintenance Release > Add AsyncForwardingAppender >

[jira] [Updated] (LOG4NET-30) Add support for type aliases in config file

[ https://issues.apache.org/jira/browse/LOG4NET-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-30: -- Fix Version/s: 1.2 Maintenance Release > Add support for type aliases in config file >

[jira] [Updated] (LOG4NET-20) [PATCH] Adds "extends" attribute to appenders

[ https://issues.apache.org/jira/browse/LOG4NET-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-20: -- Fix Version/s: 1.2 Maintenance Release > [PATCH] Adds "extends" attribute to appenders > --

[jira] [Updated] (LOG4NET-9) Programmatic configuration saving

[ https://issues.apache.org/jira/browse/LOG4NET-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-9: - Fix Version/s: 1.2 Maintenance Release > Programmatic configuration saving > -

[jira] [Updated] (LOG4NET-18) TcpAppender

[ https://issues.apache.org/jira/browse/LOG4NET-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-18: -- Fix Version/s: 1.2 Maintenance Release > TcpAppender > --- > > Key: LOG

[jira] [Updated] (LOG4NET-8) XmlSchema for everything

[ https://issues.apache.org/jira/browse/LOG4NET-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-8: - Fix Version/s: 1.2 Maintenance Release > XmlSchema for everything > > >

[jira] [Updated] (LOG4NET-6) Allow event logging on remote servers

[ https://issues.apache.org/jira/browse/LOG4NET-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-6: - Fix Version/s: 1.2 Maintenance Release I guess the original code to "check" is still available at

[jira] [Updated] (LOG4NET-5) Support layouts that generate XML instead of text

[ https://issues.apache.org/jira/browse/LOG4NET-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-5: - Fix Version/s: 1.2 Maintenance Release > Support layouts that generate XML instead of text > -

[jira] [Updated] (LOG4NET-4) Allow user to override root directory for fileappenders

[ https://issues.apache.org/jira/browse/LOG4NET-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-4: - Fix Version/s: 1.2 Maintenance Release > Allow user to override root directory for fileappenders >

[jira] [Resolved] (LOG4NET-233) Support .NET 4.0 including Client Profile

[ https://issues.apache.org/jira/browse/LOG4NET-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved LOG4NET-233. Resolution: Fixed I think - apart from some tweaks that will inevitably become necessary -

New DEBUG Snapshots of trunk - with Client Profile

Hi, I've run VS 2010's static code analysis using the security rule set on the current code base and fixed all places where it complained about transparent code referencing security-critical code or code overriding security-critical methods. The result is a bit more than the SecurityCritical attr

Re: State of Client Profile and .NET 4.0 Support

On 2011-09-04, Stefan Bodewig wrote: > On 2011-08-25, Ron Grabowski wrote: >> Is your .NET 4 support just in the NAnt scripts? > Yes, exclusively. >> It's probably safe to replace the VS2008 solution file with a VS2010 >> version. > I didn't go that far because my VS insisted on converting the

Re: Compilation Symbols

On 2011-08-21, Roy Chastain wrote: > We must have "many" conditionals. As you noted 2.0 is not a superset of > 1.1 and 4.0 is not a superset of 2.0. Because of CAS and other issues, > 2.0 and 4.0 may be in direct opposition. Agreed. > 3.0 and 3.5 are indeed supersets of 2.0, but I doubt their im