[nant-dev] [ nant-Bugs-898883 ] Unresolved dependency for COM interface when > 9

2004-02-18 Thread SourceForge.net
Bugs item #898883, was opened at 2004-02-17 12:04 Message generated for change (Comment added) made by zixthree You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=898883&group_id=31650 Category: Tasks Group: 0.8.4.0 Status: Open Resolution: None Priority: 5

Re: [nant-dev] patch for solution task

2004-02-18 Thread Gert Driesen
Vincent, I'm seeing a different behaviour here. For references to non-system assemblies, VS.NET 2003 copies assemblies locally by default. project references : default = true references to system assemblies : default = false references to non-system assemblies : default = true which matches the

[nant-dev] [ nant-Bugs-865129 ] remnants of .NET 1.0 confuse nant

2004-02-18 Thread SourceForge.net
Bugs item #865129, was opened at 2003-12-23 21:07 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=865129&group_id=31650 Category: Core >Group: 0.85 >Status: Closed >Resolution: Fixed Priority:

[nant-dev] patch for solution task

2004-02-18 Thread Vincent Labatut
Hello, the mail i sent the 16th sept 2003 is still valid and concerns also nant 8.4 final, there's a big problem with File References in the solution task. This does not concern project References. I gave all the details below. The solution Task uses the wrong default value for the "Private" attri

[nant-dev] xmlpeek and namespaces

2004-02-18 Thread Martin Aliger
Hello all,   I find one problem with xmlpeek task:     file="${prjconfig}"  xpath="Project/ExeName"  property="newexe"  failonerror="false"/> fails on XML like:   http://www.gordic.cz/shared/project-config/v_1.0.0.0">  foo   The reason is namespace associated with XML file (see

Re: [nant-dev] Bug report, dies

2004-02-18 Thread Jaroslaw Kowalski
Title: Message   Make sure your csc.exe (usually found in WINNT\Microsoft.NET\Framework\v1.1.4322) is in the PATH. This looks like a known issue with where it doesn't honor the currentframework setting. This will be fixed in future versions so that you don't need to have PATH setting at all

Re: [nant-dev] Partially failing to build from source

2004-02-18 Thread Matthias Cavigelli
[EMAIL PROTECTED] wrote: I'm pretty sure there's already a bug report for this (don't have time to check this right now). True, it has the id 865129 http://sourceforge.net/tracker/index.php?func=detail&aid=865129&group_id=31650&atid=402868 In your case, NAnt thinks that the Microsoft .NET Framework

RE: [nant-dev] Bug report, dies

2004-02-18 Thread Nicklas Norling
Title: Message What would happen if you removed the assemblyfolders tag? I can't understand why you need those. You should reference all that in the sln or VS can't compile it anyway. /Nicke -Original Message-From: Bob Peterson [mailto:[EMAIL PROTECTED] Sent: den 17 februari