Re: [nant-dev] reference assemblies and net-4.0
NHibernate solved that by building a logging proxy into NHibernate.dll and then dynamically binding to log4net. Are the licenses compatible? You could borrow their implementation. Richard On 18 May 2011, at 23:26, Ryan Boggs rmbo...@gmail.com wrote: The problem isn't NAnt targeting net-4.0-client. The problem is that one or more of NAnt's dependencies doesn't run well on the client profile. For example, log4net depends on System.Web which isn't included in the client profile. It's already been reported in NAnt's bug report while back if I remember right. Thanks, Ryan 2011/5/18 Martin Aliger martin_ali...@gordic.cz: I do not see problem _targeting_ net-4.0-client Framework. No real need to be hosted in that, imho. Martin -Original Message- From: Ryan Boggs [mailto:rmbo...@gmail.com] Sent: Wednesday, May 18, 2011 9:52 PM To: Martin Aliger Cc: nant-developers@lists.sourceforge.net Subject: Re: [nant-dev] reference assemblies and net-4.0 Hi, See inline. On Wed, May 18, 2011 at 9:19 AM, Martin Aliger martin_ali...@gordic.cz wrote: I miss some assemblies in this list (latest nightly) for net-4.0. Mostly WindowsBase and PresentationFramework. Looks like the list is not complete. Perhaps those should be added with wildcard? I need to ask about the wildcards in app.config but in the meantime, I went ahead and committed the two files in question to the app.config file. I'll perform another nightly build either tonight or tomorrow for further testing. Also there is something called NET 4.0 Client Profile. If we want to introduce this as separate Framework (targettable), there is different path for those Reference Assemblies (%ProgramFiles%\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile\Client) This was brought up in the past. I think the big issue with this right now (if I remember right) is that log4net isn't currently setup for the client profiles. I recently posted a log4net update I received on this issue to the nant-dev list but I am not sure if anything was done on their side yet. In the meantime, anyone have any thoughts on the matter? reference-assemblies basedir=${environment::get-folder-path('ProgramFiles')}/Reference Assemblies/Microsoft/Framework/.NETFramework/v4.0 include name=Microsoft.Build.Conversion.v4.0.dll/ include name=Microsoft.Build.dll/ include name=Microsoft.Build.Engine.dll/ include name=Microsoft.Build.Framework.dll/ include name=Microsoft.Build.Tasks.v4.0.dll/ include name=Microsoft.Build.Utilities.v4.0.dll/ include name=Microsoft.CSharp.dll/ include name=Microsoft.JScript.dll/ include name=Microsoft.VisualBasic.Compatibility.Data.dll/ include name=Microsoft.VisualBasic.Comptatibility.dll/ include name=Microsoft.VisualBasic.dll/ include name=Microsoft.VisualC.dll/ include name=Microsoft.VisualC.STLCLR.dll/ include name=mscorlib.dll/ include name=PresentationBuildTasks.dll/ include name=PresentationCore.dll/ include name=WindowsBase.dll/ include name=PresentationFramework.dll/ These two entries were just committed. include name=PresentationFramework.Aero.dll/ include name=PresentationFramework.Classic.dll/ include name=PresentationFramework.Luna.dll/ include name=PresentationFramework.Royale.dll/ Martin Thanks, Ryan -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net
Re: [nant-dev] reference assemblies and net-4.0
Hi, See inline... On Wed, May 18, 2011 at 3:31 PM, Dominik Guder o...@guder.org wrote: Am 18.05.2011 22:27, schrieb Martin Aliger: I do not see problem _targeting_ net-4.0-client Framework. No real need to be hosted in that, imho. Martin Hi, +1. IMHO we could require full .net 4.0 install for runtime since we need SDK anyways. I think this could be a short term solution for the time being. If I am not mistaken, I believe there was interest in supporting the client profiles in NAnt (from Gert I believe) so it could be explored. However, I don't think it will be possible until .net 1.* runtime support is dropped from NAnt. On a side note, it doesn't look like Microsoft includes MSBuild in the client profiles.. http://msdn.microsoft.com/en-us/library/cc656912.aspx Besides of this it is easy to build your own log4net and remove web related Appenders. I did this as a proof of concept. And I'm wondering why nobody is going to fix this. I'm not sure why either. It doesn't seem like any of the log4net contributors are doing much with that project anymore. Gert, please correct me if I am wrong since I see you listed as one of the active committers on their site. So far Dominik -- The answer to the great question of life, the universe and everything is 42 (Douglas Adams) -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers Thanks, Ryan -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] reference assemblies and net-4.0
NLog would be a nice replacement. Even though 2.0 is still listed as beta, it claims to support .net 2.0sp1 and up, including client profiles. But again, it would have to wait until .net 1.* runtime support is dropped from NAnt (nlog dropped support for .net 1.* starting with the 2.0 release). http://nlog-project.org/nlog2-beta1-release-notes Thanks, Ryan On Wed, May 18, 2011 at 6:15 PM, C. Mundi cmu...@gmail.com wrote: On Wed, May 18, 2011 at 3:31 PM, Dominik Guder o...@guder.org wrote: Am 18.05.2011 22:27, schrieb Martin Aliger: I do not see problem _targeting_ net-4.0-client Framework. No real need to be hosted in that, imho. Martin Hi, +1. IMHO we could require full .net 4.0 install for runtime since we need SDK anyways. Besides of this it is easy to build your own log4net and remove web related Appenders. I did this as a proof of concept. And I'm wondering why nobody is going to fix this. So far Dominik Your wondering is as valid today as it was last year when I noted that log4net seems to be a mature product abandoned after .NET 2.x. It turns out I was not completely correct. There has actually been a commit in the last year -- 7 months ago. You have to go back almost two years to find another. I have no choice but to support .NET 4 so I moved on to NLog some time ago for my own projects and have been quite happy with it. It would be nice if log4net were more actively maintained. Good Luck, Carlos -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] reference assemblies and net-4.0
Something else to look at. A quick google search says that nhibernate is LGPL. I'm not sure which version though. I am not a laywer but I would think that GPL (NAnt's current license) and LGPL would be compatible. I would appreciate additional insight if there are those who are more familiar with license compatibility than I. Thanks, Ryan On Wed, May 18, 2011 at 11:34 PM, Richard Birkby rbir...@gmail.com wrote: NHibernate solved that by building a logging proxy into NHibernate.dll and then dynamically binding to log4net. Are the licenses compatible? You could borrow their implementation. Richard On 18 May 2011, at 23:26, Ryan Boggs rmbo...@gmail.com wrote: The problem isn't NAnt targeting net-4.0-client. The problem is that one or more of NAnt's dependencies doesn't run well on the client profile. For example, log4net depends on System.Web which isn't included in the client profile. It's already been reported in NAnt's bug report while back if I remember right. Thanks, Ryan 2011/5/18 Martin Aliger martin_ali...@gordic.cz: I do not see problem _targeting_ net-4.0-client Framework. No real need to be hosted in that, imho. Martin -Original Message- From: Ryan Boggs [mailto:rmbo...@gmail.com] Sent: Wednesday, May 18, 2011 9:52 PM To: Martin Aliger Cc: nant-developers@lists.sourceforge.net Subject: Re: [nant-dev] reference assemblies and net-4.0 Hi, See inline. On Wed, May 18, 2011 at 9:19 AM, Martin Aliger martin_ali...@gordic.cz wrote: I miss some assemblies in this list (latest nightly) for net-4.0. Mostly WindowsBase and PresentationFramework. Looks like the list is not complete. Perhaps those should be added with wildcard? I need to ask about the wildcards in app.config but in the meantime, I went ahead and committed the two files in question to the app.config file. I'll perform another nightly build either tonight or tomorrow for further testing. Also there is something called NET 4.0 Client Profile. If we want to introduce this as separate Framework (targettable), there is different path for those Reference Assemblies (%ProgramFiles%\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile\Client) This was brought up in the past. I think the big issue with this right now (if I remember right) is that log4net isn't currently setup for the client profiles. I recently posted a log4net update I received on this issue to the nant-dev list but I am not sure if anything was done on their side yet. In the meantime, anyone have any thoughts on the matter? reference-assemblies basedir=${environment::get-folder-path('ProgramFiles')}/Reference Assemblies/Microsoft/Framework/.NETFramework/v4.0 include name=Microsoft.Build.Conversion.v4.0.dll/ include name=Microsoft.Build.dll/ include name=Microsoft.Build.Engine.dll/ include name=Microsoft.Build.Framework.dll/ include name=Microsoft.Build.Tasks.v4.0.dll/ include name=Microsoft.Build.Utilities.v4.0.dll/ include name=Microsoft.CSharp.dll/ include name=Microsoft.JScript.dll/ include name=Microsoft.VisualBasic.Compatibility.Data.dll/ include name=Microsoft.VisualBasic.Comptatibility.dll/ include name=Microsoft.VisualBasic.dll/ include name=Microsoft.VisualC.dll/ include name=Microsoft.VisualC.STLCLR.dll/ include name=mscorlib.dll/ include name=PresentationBuildTasks.dll/ include name=PresentationCore.dll/ include name=WindowsBase.dll/ include name=PresentationFramework.dll/ These two entries were just committed. include name=PresentationFramework.Aero.dll/ include name=PresentationFramework.Classic.dll/ include name=PresentationFramework.Luna.dll/ include name=PresentationFramework.Royale.dll/ Martin Thanks, Ryan -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] reference assemblies and net-4.0
The 450 LOC which implement this can be seen here: http://nhibernate.svn.sourceforge.net/viewvc/nhibernate/trunk/nhibernate/src/NHibernate/Logging.cs?revision=5132view=markup It binds dynamically by using compiled linq expression trees. Richard On 19 May 2011, at 19:34, Ryan Boggs rmbo...@gmail.com wrote: Something else to look at. A quick google search says that nhibernate is LGPL. I'm not sure which version though. I am not a laywer but I would think that GPL (NAnt's current license) and LGPL would be compatible. I would appreciate additional insight if there are those who are more familiar with license compatibility than I. Thanks, Ryan On Wed, May 18, 2011 at 11:34 PM, Richard Birkby rbir...@gmail.com wrote: NHibernate solved that by building a logging proxy into NHibernate.dll and then dynamically binding to log4net. Are the licenses compatible? You could borrow their implementation. Richard On 18 May 2011, at 23:26, Ryan Boggs rmbo...@gmail.com wrote: The problem isn't NAnt targeting net-4.0-client. The problem is that one or more of NAnt's dependencies doesn't run well on the client profile. For example, log4net depends on System.Web which isn't included in the client profile. It's already been reported in NAnt's bug report while back if I remember right. Thanks, Ryan 2011/5/18 Martin Aliger martin_ali...@gordic.cz: I do not see problem _targeting_ net-4.0-client Framework. No real need to be hosted in that, imho. Martin -Original Message- From: Ryan Boggs [mailto:rmbo...@gmail.com] Sent: Wednesday, May 18, 2011 9:52 PM To: Martin Aliger Cc: nant-developers@lists.sourceforge.net Subject: Re: [nant-dev] reference assemblies and net-4.0 Hi, See inline. On Wed, May 18, 2011 at 9:19 AM, Martin Aliger martin_ali...@gordic.cz wrote: I miss some assemblies in this list (latest nightly) for net-4.0. Mostly WindowsBase and PresentationFramework. Looks like the list is not complete. Perhaps those should be added with wildcard? I need to ask about the wildcards in app.config but in the meantime, I went ahead and committed the two files in question to the app.config file. I'll perform another nightly build either tonight or tomorrow for further testing. Also there is something called NET 4.0 Client Profile. If we want to introduce this as separate Framework (targettable), there is different path for those Reference Assemblies (%ProgramFiles%\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile\Client) This was brought up in the past. I think the big issue with this right now (if I remember right) is that log4net isn't currently setup for the client profiles. I recently posted a log4net update I received on this issue to the nant-dev list but I am not sure if anything was done on their side yet. In the meantime, anyone have any thoughts on the matter? reference-assemblies basedir=${environment::get-folder-path('ProgramFiles')}/Reference Assemblies/Microsoft/Framework/.NETFramework/v4.0 include name=Microsoft.Build.Conversion.v4.0.dll/ include name=Microsoft.Build.dll/ include name=Microsoft.Build.Engine.dll/ include name=Microsoft.Build.Framework.dll/ include name=Microsoft.Build.Tasks.v4.0.dll/ include name=Microsoft.Build.Utilities.v4.0.dll/ include name=Microsoft.CSharp.dll/ include name=Microsoft.JScript.dll/ include name=Microsoft.VisualBasic.Compatibility.Data.dll/ include name=Microsoft.VisualBasic.Comptatibility.dll/ include name=Microsoft.VisualBasic.dll/ include name=Microsoft.VisualC.dll/ include name=Microsoft.VisualC.STLCLR.dll/ include name=mscorlib.dll/ include name=PresentationBuildTasks.dll/ include name=PresentationCore.dll/ include name=WindowsBase.dll/ include name=PresentationFramework.dll/ These two entries were just committed. include name=PresentationFramework.Aero.dll/ include name=PresentationFramework.Classic.dll/ include name=PresentationFramework.Luna.dll/ include name=PresentationFramework.Royale.dll/ Martin Thanks, Ryan -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost
Re: [nant-dev] reference assemblies and net-4.0
I do not see problem _targeting_ net-4.0-client Framework. No real need to be hosted in that, imho. Martin -Original Message- From: Ryan Boggs [mailto:rmbo...@gmail.com] Sent: Wednesday, May 18, 2011 9:52 PM To: Martin Aliger Cc: nant-developers@lists.sourceforge.net Subject: Re: [nant-dev] reference assemblies and net-4.0 Hi, See inline. On Wed, May 18, 2011 at 9:19 AM, Martin Aliger martin_ali...@gordic.cz wrote: I miss some assemblies in this list (latest nightly) for net-4.0. Mostly WindowsBase and PresentationFramework. Looks like the list is not complete. Perhaps those should be added with wildcard? I need to ask about the wildcards in app.config but in the meantime, I went ahead and committed the two files in question to the app.config file. I'll perform another nightly build either tonight or tomorrow for further testing. Also there is something called NET 4.0 Client Profile. If we want to introduce this as separate Framework (targettable), there is different path for those Reference Assemblies (%ProgramFiles%\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile\Client) This was brought up in the past. I think the big issue with this right now (if I remember right) is that log4net isn't currently setup for the client profiles. I recently posted a log4net update I received on this issue to the nant-dev list but I am not sure if anything was done on their side yet. In the meantime, anyone have any thoughts on the matter? reference-assemblies basedir=${environment::get-folder-path('ProgramFiles')}/Reference Assemblies/Microsoft/Framework/.NETFramework/v4.0 include name=Microsoft.Build.Conversion.v4.0.dll/ include name=Microsoft.Build.dll/ include name=Microsoft.Build.Engine.dll/ include name=Microsoft.Build.Framework.dll/ include name=Microsoft.Build.Tasks.v4.0.dll/ include name=Microsoft.Build.Utilities.v4.0.dll/ include name=Microsoft.CSharp.dll/ include name=Microsoft.JScript.dll/ include name=Microsoft.VisualBasic.Compatibility.Data.dll/ include name=Microsoft.VisualBasic.Comptatibility.dll/ include name=Microsoft.VisualBasic.dll/ include name=Microsoft.VisualC.dll/ include name=Microsoft.VisualC.STLCLR.dll/ include name=mscorlib.dll/ include name=PresentationBuildTasks.dll/ include name=PresentationCore.dll/ include name=WindowsBase.dll/ include name=PresentationFramework.dll/ These two entries were just committed. include name=PresentationFramework.Aero.dll/ include name=PresentationFramework.Classic.dll/ include name=PresentationFramework.Luna.dll/ include name=PresentationFramework.Royale.dll/ Martin Thanks, Ryan -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] reference assemblies and net-4.0
The problem isn't NAnt targeting net-4.0-client. The problem is that one or more of NAnt's dependencies doesn't run well on the client profile. For example, log4net depends on System.Web which isn't included in the client profile. It's already been reported in NAnt's bug report while back if I remember right. Thanks, Ryan 2011/5/18 Martin Aliger martin_ali...@gordic.cz: I do not see problem _targeting_ net-4.0-client Framework. No real need to be hosted in that, imho. Martin -Original Message- From: Ryan Boggs [mailto:rmbo...@gmail.com] Sent: Wednesday, May 18, 2011 9:52 PM To: Martin Aliger Cc: nant-developers@lists.sourceforge.net Subject: Re: [nant-dev] reference assemblies and net-4.0 Hi, See inline. On Wed, May 18, 2011 at 9:19 AM, Martin Aliger martin_ali...@gordic.cz wrote: I miss some assemblies in this list (latest nightly) for net-4.0. Mostly WindowsBase and PresentationFramework. Looks like the list is not complete. Perhaps those should be added with wildcard? I need to ask about the wildcards in app.config but in the meantime, I went ahead and committed the two files in question to the app.config file. I'll perform another nightly build either tonight or tomorrow for further testing. Also there is something called NET 4.0 Client Profile. If we want to introduce this as separate Framework (targettable), there is different path for those Reference Assemblies (%ProgramFiles%\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile\Client) This was brought up in the past. I think the big issue with this right now (if I remember right) is that log4net isn't currently setup for the client profiles. I recently posted a log4net update I received on this issue to the nant-dev list but I am not sure if anything was done on their side yet. In the meantime, anyone have any thoughts on the matter? reference-assemblies basedir=${environment::get-folder-path('ProgramFiles')}/Reference Assemblies/Microsoft/Framework/.NETFramework/v4.0 include name=Microsoft.Build.Conversion.v4.0.dll/ include name=Microsoft.Build.dll/ include name=Microsoft.Build.Engine.dll/ include name=Microsoft.Build.Framework.dll/ include name=Microsoft.Build.Tasks.v4.0.dll/ include name=Microsoft.Build.Utilities.v4.0.dll/ include name=Microsoft.CSharp.dll/ include name=Microsoft.JScript.dll/ include name=Microsoft.VisualBasic.Compatibility.Data.dll/ include name=Microsoft.VisualBasic.Comptatibility.dll/ include name=Microsoft.VisualBasic.dll/ include name=Microsoft.VisualC.dll/ include name=Microsoft.VisualC.STLCLR.dll/ include name=mscorlib.dll/ include name=PresentationBuildTasks.dll/ include name=PresentationCore.dll/ include name=WindowsBase.dll/ include name=PresentationFramework.dll/ These two entries were just committed. include name=PresentationFramework.Aero.dll/ include name=PresentationFramework.Classic.dll/ include name=PresentationFramework.Luna.dll/ include name=PresentationFramework.Royale.dll/ Martin Thanks, Ryan -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] reference assemblies and net-4.0
Am 18.05.2011 22:27, schrieb Martin Aliger: I do not see problem _targeting_ net-4.0-client Framework. No real need to be hosted in that, imho. Martin Hi, +1. IMHO we could require full .net 4.0 install for runtime since we need SDK anyways. Besides of this it is easy to build your own log4net and remove web related Appenders. I did this as a proof of concept. And I'm wondering why nobody is going to fix this. So far Dominik -- The answer to the great question of life, the universe and everything is 42 (Douglas Adams) -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers