Menu
▾
▴
[nant-dev] [ nant-Bugs-1579653 ] solution task problem with VB.NET compilation constants
|
From: SourceForge.net <no...@so...> - 2006-10-18 12:58:09
|
Bugs item #1579653, was opened at 2006-10-18 12:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1579653&group_id=31650 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Tasks Group: 0.85 Status: Open Resolution: None Priority: 5 Submitted By: s_tracey (s_tracey) Assigned to: Nobody/Anonymous (nobody) Summary: solution task problem with VB.NET compilation constants Initial Comment: If you have a .NET solution consisting of a VB.NET project that has conditional compilation constants containing string literals defined e.g .VBProj contains line: DefineConstants = 'NAME="Value"' (this is how VS represents ccc's in .VBProj file) Then the <solution> task fails to properly present these constants to vbc, hence breaking build. If you use the <vbc> task, then this only works properly if you prepend quotes with a "\". e.g This does not work: <vbc .... define="NAME="Value;"" ... But this does: <vbc .... define="NAME=\"Value\"" ... This is because of a known problem with the .NET vbc compiler (.NET 10, 1.1 and 2.0 I believe)(which <vbc> task maps to) - see MS kb 818217 I suspect problem is that <solution> task does not prepend the "\" when formulating the define attribute values. Should be a quick fix for someone which would certainly add a lot of value to me. Looking to automate build/test of several large VB.NET solutions which rely heavily on conditional compilation constants. There is also an argument for adding the fix to <vbc> task as well. Until then, am stuck with using XSLT to transform .vbproj to .build script, which is not ideal. If you need an example, let me know. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1579653&group_id=31650 |