Brad,
This issue should be fixed in the next nightly build.
Thanks for the report !
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: [Nan
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)
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
o: NAnt Users
> Subject: [Nant-users] Problem with resgen inside a task
>
> 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
>
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
