Okay, I found the problem.
Basically, it boils down to the way CompilerBase is calculating the
manifest resource name. If you look inside
CompilerBase.GetManifestResourceName (the one with 4 parameters), in
ComputerBase.cs, you'll see:
if (resourceLinkage != null && resourceLinkage.IsValid)
I tried the most recent nightly build and still didnt have any luck, I get
the following error:
C:\coreytest\nant_script\test.build(27,4):
Error loading assembly 'SecantCommon.dll'.
File or assembly name SecantCommon.dll, or one of its dependencies, was
not found.
Total time: 0.1 seconds.
he
Corey,
Can you try using a recent nightly build of NAnt
(http://nant.sourceforge.net/nightly/builds) ?
Thanks !
Gert
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Corey Krehel
> Sent: maandag 15 november 2004 23:13
> To: [EMAIL PROTECTED]
>
I am attempting to use the script tag to execute tasks based on the success
or failure of my project.
In order to do everything I want to do, I am attempting to use classes in
one of my application dlls.
Below is a copy of the test project I have created:
No, that's okay. If it's not a known problem, I'll fix it today (I
really need a fix today)... then presumably post a patch to the
developers list, I guess.
- Brad
On Mon, 15 Nov 2004 21:38:29 +0100, Gert Driesen
<[EMAIL PROTECTED]> wrote:
> Hi Brad,
>
> Its definitely not a known issue. If you
Hi Brad,
Its definitely not a known issue. If you can provide a small repro, I'd be
happy to look into it.
Gert
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Brad Wilson
> Sent: maandag 15 november 2004 21:08
> To: NAnt Users
> Subject: [Nant
I Google'd and searched the archives, but couldn't find an answer.
I'm having a problem with the task and resgen.
Specifically, one of my .resx files (which contains 0 resources, by
the way) won't compile, and I believe the problem is that NAnt is
incorrectly forumlating the command line.
I turn
Gert Driesen wrote:
Hi,
Right now, the zip & tar flavors of our distributions have the same content.
I wonder if it makes sense to include the SDK docs in HTML Help format for
the (gzipped) tar flavor, as these target *nux anyway.
that probably doesn't make much sense if we assume that Windows u
Hi,
Right now, the zip & tar flavors of our distributions have the same content.
I wonder if it makes sense to include the SDK docs in HTML Help format for
the (gzipped) tar flavor, as these target *nux anyway.
Should we replace the HTML Help format SDK doc with the plain HTML format
for the tar