Robert, I ran into an issue with license files too a couple weeks ago and solved it by installing the licensed component stuff on the build box. This is probably one difference between your dev boxes and your build box.
The other thing I did was to modify the licenses.licx file to contain version, culture, and the public key token. It's an undocumented format as far as I know, but it worked for me. I posted my solution to this list under the subject "Licenses.licx and ActiveReports solution". See that post for more details on how to modify the licenses.licx file: http://sourceforge.net/mailarchive/forum.php?thread_id=5550904&forum_id= 9544 Hope this helps, Oran -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Gomes Sent: Tuesday, September 21, 2004 11:03 AM To: Gert Driesen; [EMAIL PROTECTED] Subject: RE: [Nant-users] <solution> task produces assemblies that crash -- vs.net doesn't Gert, Ran against the nightly for NAnt/NAntcontrib 0.85. It appeared to bomb out attempting to compile the final assembly (the Windows Forms executable). Here's the error (as well as the warnings recommending include over fileset): ----- ----- ----- [license] Creating Licenses file C:\DOCUME~1\AUTOBU~1.DEV\LOCALS~1\Temp\tmp13B.tmp\watchcaptain.richclien t.exe.licenses... [solution] External Program Failed: C:\DOCUME~1\AUTOBU~1.DEV\LOCALS~1\Temp\tmp13B.tmp\lc.exe (return code was -1): [solution] NAnt.Core.BuildException: External Program Failed: C:\DOCUME~1\AUTOBU~1.DEV\LOCALS~1\Temp\tmp13B.tmp\lc.exe (return code was -1) [solution] at NAnt.Core.Tasks.ExternalProgramBase.ExecuteTask() in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp145F.tmp\src\NAnt.Core\Tasks\ExternalProgramBase.cs:lin e 311 [solution] at NAnt.DotNet.Tasks.LicenseTask.ExecuteTask() in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp145F.tmp\src\NAnt.DotNet\Tasks\LicenseTask.cs:line 371 [solution] at NAnt.Core.Task.Execute() in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp145F.tmp\src\NAnt.Core\Task.cs:line 177 [solution] at NAnt.VSNet.Resource.CompileLicx(ConfigurationSettings configurationSettings) in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp145F.tmp\src\NAnt.VSNet\Resource.cs:line 211 [solution] at NAnt.VSNet.Resource.Compile(ConfigurationSettings configurationSettings) in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp145F.tmp\src\NAnt.VSNet\Resource.cs:line 88 [solution] at NAnt.VSNet.Project.Build(ConfigurationBase configurationSettings) in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp145F.tmp\src\NAnt.VSNet\Project.cs:line 352 [solution] at NAnt.VSNet.ProjectBase.Compile(String configuration) in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp145F.tmp\src\NAnt.VSNet\ProjectBase.cs:line 188 [solution] at NAnt.VSNet.Solution.Compile(String configuration) in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp145F.tmp\src\NAnt.VSNet\Solution.cs:line 363 [solution] at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp145F.tmp\src\NAnt.VSNet\Tasks\SolutionTask.cs:line 385 [solution] at NAnt.Core.Task.Execute() in C:\Documents and Settings\drieseng\Local Settings\Temp\tmp145F.tmp\src\NAnt.Core\Task.cs:line 169 \\dev-main\wcbuilds\WCBuilds\Common\build.build(21,5): Element <includesList... /> for <fileset... /> is deprecated. Use <includesfile> instead. \\dev-main\wcbuilds\WCBuilds\Common\build.build(26,19): Element <includes... /> for <fileset... /> is deprecated. Use <include> element instead. ----- ----- ----- What information do you recommend I include in the repro for the bug report, and to where should it be directed? Thanks. Rob Gomes Senior Applications Developer P: 508-748-2121 F: 508-748-2707 E: [EMAIL PROTECTED] -----Original Message----- From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 21, 2004 2:12 PM To: Robert Gomes; [EMAIL PROTECTED] Subject: Re: [Nant-users] <solution> task produces assemblies that crash -- vs.net doesn't Robert, Would it be an option for you to upgrade to a recent nightly build (http://nant.sourceforge.net/nightly/builds) as a first step ? If you can still reproduce the issue using the nightly builds, then I suggest creating a bug report and attaching a small repro to it. Gert ----- Original Message ----- From: "Robert Gomes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 21, 2004 7:57 PM Subject: [Nant-users] <solution> task produces assemblies that crash -- vs.net doesn't Greetings List Subscribers, I appear to be having some issues with the <solution> task in nAnt 0.84. Here's the overview: ----- ----- When compiled on a developer's workstation (VS.NET 2003), the output can be successfully executed on both the developer's workstation and the build workstation. When compiled on the build workstation (nAnt and .NET SDK 1.1), the output crashes immediately upon execution on both the developer's workstation and the build workstation. The return code is -1073741819. The event logged in the Application Event Log is: "Faulting application watchcaptain.richclient.exe, version 1.0.1725.22895, faulting module unknown, version 0.0.0.0, fault address 0xf3f7d08c." The <solution> task produces the same number of assemblies (with the same names) as VS.NET does, however, for some assemblies there are some slight size discrepencies (an occasional 1-2KB) which tips me off that the <solution> task is doing something slightly different than VS.NET. ----- ----- I'm running nAnt 0.84, and the .NET Framework 1.1 (with SDK installed). I have confirmed that the solution is compiled using the 1.1 framework. My <solution> task is fairly straightforward: <property name="nant.settings.currentframework" value="net-1.1"/> <solution configuration="${build.config}" solutionfile="${build.sln.file}" verbose="true" failonerror="true" /> The error persists despite which configuration I use (debug or release in this case). There is only one solution file, so yes, it is using the correct solution file. I've also removed and reinstalled the .NET Framework and SDK out of pure paranoia. ----- ----- Everything else works great! Dynamic versioning, grabbing items from sourcesafe, labeling, VB.Doc, nDoc, NUnit and Nunit report... just the darn thing won't build properly. Any and all help is greatly appreciated. Thanks again. Rob Gomes Senior Applications Developer P: 508-748-2121 F: 508-748-2707 E: [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
