1239458
> Conditional compilation symbols for .net4 Release
> -
>
> Key: LOG4NET-322
> URL: https://issues.apache.org/jira/browse/LOG4NET-322
> Project: Log4net
>
yself
> Conditional compilation symbols for .net4 Release
> -
>
> Key: LOG4NET-322
> URL: https://issues.apache.org/jira/browse/LOG4NET-322
> Project: Log4net
> Issue Type:
Conditional compilation symbols for .net4 Release
-
Key: LOG4NET-322
URL: https://issues.apache.org/jira/browse/LOG4NET-322
Project: Log4net
Issue Type: Bug
Components: Builds
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
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.
3.0 and 3.5 are indeed supersets of 2.0, but I doubt their importance as
conditionals. I would only see them as i
Hi all,
before I started to modifiy things for 4.0 and client profile the NAnt
build was setting a compilation symbol for the "family" like "NET",
"NETCF", "MONO" and one for the specific version "NET_1_1", "NET_2_0"
and so on. Also the conditional compilation sections seem to not assume
NET_2_0
