Jason,
Thanks for this. I'll review the change tonight.
Thanks for the suggestions. I've responded to each below. This patch only works with non-resx files. I took a look at the code that's currently handling the resx part and didn't feel comfortable enough with the context to mess with that c
Bob,
the sourcesafe tasks are in NAntContrib. see
http://sourceforge.net/projects/nantcontrib for cvs instructions.
Ian
I see there is a SourceSafe reference under Nant\src\Extras. How do I
get the code or at least more info on whats there?
Thanks, Bob
-Original Message-
From: [EMAIL
I see there is a SourceSafe reference under Nant\src\Extras. How do I
get the code or at least more info on whats there?
Thanks, Bob
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-users-request@;lists.sourceforge.net]
Sent: Wednesday, November 06, 2002 1:24 PM
To: [EMAIL PROTEC
Thanks for the suggestions. I've responded to each below. This patch only works with
non-resx files. I took a look at the code that's currently handling the resx part and
didn't feel comfortable enough with the context to mess with that code. Should be an
easy change for someone who knows wh
I see there is a SourceSafe reference under Nant\src\Extras. How do I
get the code or at least more info on whats there?
Thanks, Bob
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-users-request@;lists.sourceforge.net]
Sent: Wednesday, November 06, 2002 12:57 PM
To: [EMAIL PROT
Jason,
As Tomas said please send in your patch. Its been quite diffucult to
mimic visual studio's semantics with regard to handling the .resx files.
I like your idea of dynamic prefixes.
Ian
We have a project with quite a few embedded non-resx resource files at different folder depths. The pre
Jason,
<<
We have a project with quite a few embedded non-resx resource files at
different folder depths. The prefix attribute does not correctly mimic the
VS.NET behavior for generating manifest resource names.
We have made a small change to the source to add a dynamicprefix boolean
attribute.
Thanks. Apparently I don't know as much about my CVS client as I wish I did. And
getting the latest snapshot also found the resgen task. Now I have to focus on
getting slingshot to work with the new VS.NET codename Everett...apparently it uses a
new .sln format.
Again, thank you for your hel
Hello Seth,
The 'ExpandProperties' error is due to the fact that the NAnt version used is out of
date with regard to the NAntContrib version used.
I recommend downloading the latest NAnt version from
http://nant.sourceforge.net/snapshot/
Best regards,
Bernard
> -Original Message-
>
Okay, I give up. I think I've been able to get the NAntContrib project to build twice
since August. The error I keep getting is this:
C:\Code\cvs\NAntContrib\src\Util\SqlStatementList.cs(223,17): error CS0117:
'SourceForge.NAnt.PropertyDictionary' does not contain a definition for
'ExpandProp
We have a project with quite a few embedded non-resx resource files at different
folder depths. The prefix attribute does not correctly mimic the VS.NET behavior for
generating manifest resource names.
We have made a small change to the source to add a dynamicprefix boolean attribute.
When se
Originally I imagined an env attribute just for the exec task, for instance
Of course, it might be useful if the env attribute could be used for other
tasks as well.
Patrick
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:nant-users-admin@;lists.sourceforge.net]On Behal
Title: RE: [Nant-users] Trouble using taskdef
If you want this to work,the assembly name where your customs task are located, must end with "Tasks" (see the TaskFactory class line 59)
Yves
> -Original Message-
> From: Gordon Weakliem [mailto:[EMAIL PROTECTED]]
> Sent: 04 November
13 matches
Mail list logo
