[
https://issues.apache.org/jira/browse/LOG4NET-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254645#comment-13254645
]
Dominik Psenner commented on LOG4NET-233:
-----------------------------------------
That's why you have to define it. :-) Clicking on the link above and following
one of the first 3 search results (at least which ones I have tried) shows you
how to achieve that with visual studio. What you cannot do is building log4net
from source and expecting that visual studio builds all different dll's for
.net 3.5, 4.0, 4.0 client profile since visual studio does not allow you to
change the target profile of a project at build-time. What are you trying to
achieve that requires you to not use a precompiled log4net dll?
> Support .NET 4.0 including Client Profile
> -----------------------------------------
>
> Key: LOG4NET-233
> URL: https://issues.apache.org/jira/browse/LOG4NET-233
> Project: Log4net
> Issue Type: New Feature
> Components: Appenders, Builds, Core, Documentation, Examples, Other
> Affects Versions: 1.2.10
> Environment: Windows XP, Vista, 7 - .Net 4.0
> Reporter: Daniel McGloin
> Fix For: 1.2.11
>
> Attachments: 233b.patch, NET4.patch, log4net-1.2.10-net-4.0.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Please add a release targeting .NET 4.0 (currently in Beta 2). In addition,
> to support the .NET 4.0 Client Profile, divide any server-side parts into a
> separate library set that can be optionally referenced/deployed..
--
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
