[ 
https://issues.apache.org/jira/browse/LOG4NET-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683361#action_12683361
 ] 

ghinwa badawi commented on LOG4NET-207:
---------------------------------------

Please note that I downgraded the .net framework of the windows service to
2.0  and still facing the same bug, the same message is being displayed.

is there a solution for this ?

I don't know if this is the right place to ask for help, if not then please
provide me with the correct forum for this.

Thanks,
Ghinwa






> Could not find schema information for the element 'log4net'
> -----------------------------------------------------------
>
>                 Key: LOG4NET-207
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-207
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 1.2.10
>         Environment: visual studio 2008 with .net 3.5
>            Reporter: ghinwa badawi
>            Priority: Blocker
>
> Hi,
> i have tried to use log4net in a windows service on VS2008 - .Net Framework: 
> 3.5,
> I added the following in the app.config file :
> <configSections>
>     <section name="log4net" 
> type="log4net.Config.Log4NetConfigurationSectionHandler, log4net" />
>   </configSections>
>  
>   <log4net>
>     <appender name="FileAppender" type="log4net.Appender.FileAppender">
>       <file value="C:\logfile.txt" />
>       <appendToFile value="true" />
>       <layout type="log4net.Layout.PatternLayout">
>         <conversionPattern value="%date [%thread] %-5level %logger 
> [%property{NDC}] - %message%newline" />
>       </layout>   
>     </appender>
>     <root>
>       <level value="DEBUG" />
>       <appender-ref ref="FileAppender" />
>     </root>
>   </log4net>
>  
> but i am getting the below message:
> "Message    5    Could not find schema information for the element 'log4net'. 
>    

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to