> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Mateusz Loskot
> Sent: dinsdag 7 december 2004 3:44
> To: [EMAIL PROTECTED]
> Subject: Re: [Nant-users] WinForms, Images, Resources
>
> User Gert Driesen wrote::
> > If you want to have manifest
Title: compile-time option on solution
I'm using NANT to build a solution (primarily a web project, and its supporting project).
How do I specify that I want 'OPTION COMPARE TEXT' to be used across the entire build?
Hello everyone,
Has anyone seen a problem like this? (this is a contrived example of
the problem)
For some strange reason, when I stop the debugger at BP #1, for the
first time, table_ is **already initialized to a Hashtable, count = 0 (when it
should be null, and thus step into
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Ian MacLean
> Sent: dinsdag 7 december 2004 3:43
> To: John Ellenberger
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Nant-users] LoadFile in .85 RC1
>
> John Ellenberger wrote:
>
> > I'm hoping someo
User Ryan Cromwell wrote::
Well if you want to be cynical about it, yes I'm sure they have many
outs. :)
Honestly, I'm in this situation ;-)
I'll bet when Wilbert gets ahold of PSS, they'll get him to
a tech pretty quickly and they'll be able to get it cleared up.
That's great.
It may very well be
Well if you want to be cynical about it, yes I'm sure they have many
outs. :) I'll bet when Wilbert gets ahold of PSS, they'll get him to
a tech pretty quickly and they'll be able to get it cleared up. It
may very well be that they chose not to use encoded Xml for a good
reason... we all make in
User Gert Driesen wrote::
If you want to have manifest resource names that match those generated by
VS.NET, you should avoid usign .
Instead, you should use the element of the individual compiler
tasks and have the compiler task do the resource compilation (and generation
of the manifest resource
John Ellenberger wrote:
I'm hoping someone can help answer a question in regards to the
LoadFile task. It's actually not the task itself, but associated
functionality. Here's the dilemma:
I'm checking an AssemblyInfo.vb file out, and want to update the
'AssemblyVersion' key with the value fr
User Ryan Cromwell wrote::
I don't think it's too late. I would suggest that this issue be
documented and *IF* it's an MS bug, a link or reference to a PSS
Hotfix be made available. That way those who hit the issue can
resolve it on the end where it's being caused.
Funny thing, there is "XML" wor
Hi Marijn,
The problem here is that you did not build the mono 2.0 profile, but Mono
still assumes the 2.0 profile is available (which I reported as Mono bug
#62913, http://bugzilla.ximian.com/show_bug.cgi?id=62913).
NAnt is indeed trying to the the mono-2.0 "framework", as this is the
identifier
Title: Message
Greets
folks!
I'm hoping someone can help
answer a question in regards to the LoadFile task. It's actually not the
task itself, but associated functionality. Here's the
dilemma:
I'm checking an AssemblyInfo.vb
file out, and want to update the 'AssemblyVersion' key with th
Hi Listers,
We're setting up a C# project that should be compilable in both Linux
and Windows. So, I am trying to get Nant to compile under Mono 1.1 with
Linux, but when running make it complains. I know that I have to select
the correct framework to build (and it's not mono-2.0), and that
instrun
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Wilbert van Dolleweerd
> Sent: maandag 6 december 2004 21:07
> To: 'NAnt Users'
> Subject: RE: [Nant-users] Known bug in Nant?
>
> > I don't think it's too late. I would suggest that this issue
> I don't think it's too late. I would suggest that this issue
> be documented and *IF* it's an MS bug, a link or reference to
> a PSS Hotfix be made available. That way those who hit the
> issue can resolve it on the end where it's being caused.
>
> The friendly error/exception message is st
06.12 2004 r., on 08:26 Merrill Cornish wrote:
> >>> XML is a standard and IMHO is specified to be followed.
>
> True, but not relevant to this case.
>
> If advertises that it processes Visual Studio solution files, then
> it should process Visual Studio soution files whatever their format. I
I don't think it's too late. I would suggest that this issue be
documented and *IF* it's an MS bug, a link or reference to a PSS
Hotfix be made available. That way those who hit the issue can
resolve it on the end where it's being caused.
The friendly error/exception message is still a must thou
Brad Wilson wrote:
It's too late, really. Even if they fix this for 2.0, the
task will need to parse 1.0 and 1.1 project files far into the future,
and thus the code will need to exist. It's, ironically, less work if
they don't fix it, since it will prevent needing to have two codepaths
(one for 1
It's too late, really. Even if they fix this for 2.0, the
task will need to parse 1.0 and 1.1 project files far into the future,
and thus the code will need to exist. It's, ironically, less work if
they don't fix it, since it will prevent needing to have two codepaths
(one for 1.x project files an
>>> XML is a standard and IMHO is specified to be followed.
True, but not relevant to this case.
If advertises that it processes Visual Studio solution files, then
it should process Visual Studio soution files whatever their format. If
does NOT process Vusual Studio solution files, then it
Has anyone contacted either the MSDN newsgroups or MS support to
report what very well could be a bug? Then everyone would be happy :)
On Mon, 6 Dec 2004 08:26:06 -0600 (GMT-06:00), Merrill Cornish
<[EMAIL PROTECTED]> wrote:
> >>> XML is a standard and IMHO is specified to be followed.
>
> True
Hi Gert,
With reference to the error below i.e 'error BC30560: 'VpDataWrap' is
ambiguous in the namespace 'VPDal5'.', I think it is because nant try to
copy/overwrite the COM dll (VPDal5) for the second time. The dll was
succesfully copied to ouput folder by earlier project.
Is the a way to exc
21 matches
Mail list logo
