[
https://issues.apache.org/jira/browse/LOG4NET-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-176:
-----------------------------------
Fix Version/s: (was: v.Next)
1.2.11
Solution and project files went into trunk with svn revision 881070
Current trunk builds for 3.5 and 4.0 (when using NAnt 0.91 alpha2, that is),
What we don't have in trunk right now are compilation symbolds for 3.5 (not
sure why we'd need them ATM) and separate names. Is it important to have those?
> Buildable with VS 2008 and .NET FW 3.5
> --------------------------------------
>
> Key: LOG4NET-176
> URL: https://issues.apache.org/jira/browse/LOG4NET-176
> Project: Log4net
> Issue Type: New Feature
> Components: Builds
> Environment: Windows, log4net trunk, vs 2008 .net 3.5
> Reporter: Nicklas Norling
> Priority: Minor
> Fix For: 1.2.11
>
> Attachments: Vs2k8.net35.patch
>
>
> Providing a patch for the changes I'm using when compiling log4net locally
> using vs2008 and .net 3.5. The patch is created against trunk @ 701632. It
> adds project and solution files for vs 2008, adds compilation symbol NET_3_5
> which is then added to all conditional compilation statements that have
> NET_2_0 today. Also the AssemblyInfo.cs has a .NET 3.5 section added. Since
> the project files have to be manually updated when new files are added to
> trunk I would appretiate it if this patch (or one with similar functions)
> where added to trunk.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
