Hi Gert,

I actually handed the whole lc.exe problem over to my boss, who has
experienced a similar thing before because I couldn't even get it to
work from the command line.  It seems there may have been a problem with
the .licx file in that the module that the licensed class resides in was
not specified... However, it builds fine from Visual Studio, and the
solution suggested by Oran which is basically the same also refused to
work, so I don't know.  I need to retest this.

In the meantime I wrote a quick task, which I'm happy to post to the
list if people would find it useful, to build using Visual Studio's
devenv.exe.  It seems to work fine with VS.NET 2002, but I couldn't
speak to its reliability with 2003.

All of that said, my plan is actually NOT to use Visual Studio for
builds in the long-term to avoid the possibility of a developer screwing
up builds on the build server because they've managed to corrupt their
project, so I'll be revisiting the lc.exe issue, hopefully some time
next week.


Thanks,
Bart



======================
Bart Read
Software Engineer
Red Gate Software Ltd
+44 (0) 870 160 0037 ext 31
======================

-----Original Message-----
From: Gert Driesen [mailto:[EMAIL PROTECTED] 
Sent: 09 October 2004 08:28
To: Bart Read; [EMAIL PROTECTED]
Subject: Re: [Nant-users] References from solution do not appear to be
persisted in LicenseTask

Bart,

License compilation has always been problematic, assembly/project
reference are not actually passed to lc.exe as there's a bug in that
tool. Instead we copy the assembly/project references and lc.exe to a
temp directory, and execute it from there. That way it should be able to
resolve all references.

I would be grateful if you could send me a complete repro (including the
assemblies for licensed components).

Gert
----- Original Message -----
From: "Bart Read" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 08, 2004 6:54 PM
Subject: [Nant-users] References from solution do not appear to be
persisted in LicenseTask


Dear All,





I'm having problems compiled a project using the <solution> task.  The
solution uses the .NET licensing support and incorporates a .licx file.
However, when the license task attempts to compile the license I get the
following output:



F:\integration\Halibut\Build>nant -D:integrationRoot=F:\integration
-D:version=1.0.0 -D:debug=true -buildfile:juscruisin.build build

NAnt 0.85 (Build 0.85.1740.0; net-1.0.win32; nightly; 06/10/2004)

Copyright (C) 2001-2004 Gerry Shaw

http://nant.sourceforge.net



Buildfile: file:///F:/integration/Halibut/Build/juscruisin.build

Target(s) specified: build





buildCommon:



 [solution] Starting solution build.

 [solution] Building 'CommonCLI' [Debug] ...



buildNewtDll:



 [solution] Starting solution build.

 [solution] Building 'NewtCLI' [Debug] ...

              [license] Processing complist
'F:\integration\Halibut\1.0.0\NewtDl

l\licenses.licx'...

              [license]
F:\integration\Halibut\1.0.0\NewtDll\licenses.licx(1) :

error LC0003 : Unabled to resolve type 'xxx.xxx.xxx.xxx'

              [license] Creating Licenses file
C:\DOCUME~1\BART~1.REA\LOCALS~1\T

emp\tmp2010.tmp\xxx.xxx.xxx.dll.licenses...



BUILD FAILED



External Program Failed:
C:\DOCUME~1\BART~1.REA\LOCALS~1\Temp\tmp2010.tmp\lc.exe

 (return code was -1)



Total time: 1.3 seconds.



It seems as though the project references are not being passed in to the
license task, which causes it to fail when attempting to resolve the
type referenced in the .licx file.  Anybody have any ideas about this?
Am I doing something wrong or is this a bug?  I'm using the NAnt 0.85
nightly build from 6th October as I'm running with CruiseControl.NET (or
at least I will be) and 0.84 doesn't embed error messages correctly in
the XML log.  The task in my build file that fails is as follows:



<target name="buildNewtDll" depends="buildCommon" description="xxxx">

            <solution

                        configuration="${solutionConfiguration}"

                        includevsfolders="true"

                        outputdir="${buildDir}">

                        <projects>

                                    <include
name="${newtDllBase}\NewtCLI.csproj"/>

                        </projects>

            </solution>

    </target>



Any help would be gratefully received.





Many thanks,



======================

Bart Read

Software Engineer

Red Gate Software Ltd

+44 (0) 870 160 0037 ext 31

======================






-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to