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

Stefan Bodewig commented on LOG4NET-319:
----------------------------------------

There shouldn't be any dependency on the CLR 2.0 in the build as it is.

The only things your patch changes is thr project GUID, the output path and 
whether NET_2_0 is defined (and it has to be defined in order to get a working 
4.0 version).

I'm afraid I don't understand what kind of problem you are trying to solve.  
The solution creates a "real" 4.0 assembly.

Please also note that the Solution file is there to help other developers only, 
the real build system for log4net is NAnt.
                
> .Net 4.0 build
> --------------
>
>                 Key: LOG4NET-319
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-319
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Builds
>    Affects Versions: 1.2.11, 1.2.12
>         Environment: Nothing special
>            Reporter: NN
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> Currently log4net.vs2010 doesn't build log4net for .Net 4.0 but for .Net 2.0
> This patch adds additional project to build only for .Net 4.0 without 2.0 
> dependencies.
> The change is here: https://github.com/apache/log4net/pull/2/files
> It just adds another project and puts it in solution.
> Nothing special.
> Another option is to set .Net 4.0 build for log4net.vs2010.csproj
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to