Dante Omar Villarreal wrote:
I moved some common .Net DLLs to a Network drive, again, the IDE
builds the solution fine but using the task throws the
following error, any help appreciated, this is somewhat urgent.
*Error resolving module references of 'N:\DSIP.DataBus.dll'.:
NAnt.Core.BuildExce
Gert,
Thanks for the response. I like the detail
on this page a lot better than on the “stable” page, BTW. J
The solution to my problem involved removing
an NDoc.Documenter.Msdn.dll version 1.2.1303.41355 from my \bin and
\lib directories.
I don’t know why the version of NDoc.D
Eric,
See http://nant.sourceforge.net/nightly/latest/help/tasks/ndoc.html for
instructions on how to make other NDoc documenters available for use by the
task.
Hope this helps,
Gert
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
DeslauriersSent: woens
I moved some common .Net DLLs to a Network drive, again, the IDE builds the solution fine but using the task throws the following error, any help appreciated, this is somewhat urgent.
Error resolving module references of 'N:\DSIP.DataBus.dll'.:NAnt.Core.BuildException: Error resolving module ref
Gert,
I resolved this issue but I thought I'd report this to you. Here's the scenario:
Like any big project, several people have worked on the 55+ projects that are part of the solution I am now building through NAnt (well, it is no longer a single solution) but it looks like at some point some
Hmm. Thanks for that. I wasn't using the basedir attribute. I'll have to try it tomorrow morning. This is for an automated build which I don't want to disrupt until then. That makes sense to me. I should have RTFMed a bit better. Also, thanks everyone for your interest. If I continue to have troubl
Hmm. I'll have to think about that. We have a pretty complex build that involves some VB.NET, VB6 and a lot of C++. We check the solution file in because it handles the dependencies, which are kind of complex. We're in the middle of a migration to .NET which will slowly begin to simplify things. Th
Bill,
The task does support building Visual C++ projects. However, I
can't guarantee that won't be running into problems (although many
improvements/fixes have been introduced lately). I can only guarantee that
any issue you run into will be fixed asap.
Gert
- Original Message -
From:
Christopher,
>>> TreatWarningsAsErrors = "true". in the csproj files.
OK, what does TreatWarningsAsErrors = "true" actually _do_? At what level does
it work? Does it possibly simply say the solution build stops on warnings,
which it wouldn't normally do.
If the program that uses the TreatWar
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Gert Driesen
[snip]
> PS. What are the issues that you're running into with the
> task ?
Perhaps I am gun-shy from the days of checking .dsw's into the source
control and building with them, b
Dustin,
This is how I use devenv using the task:
Does this help?
Felice
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gert Driesen
Sent: Wednesday, January 05, 2005 8:26 AM
To: Dustin Aleksiuk; nant-users@lists.sourceforge.net
Subject: Re: [Nant-user
Hi Merrill, Thanks for the reply. I tried all manner of quotes around it, if that's what you mean. I tried: program='"D:\APPS\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.exe"'program='D:\APPS\"Microsoft Visual Studio .NET 2003"\Common7\IDE\devenv.exe' The odd thing is that on the command l
Title: Message
I use
the basedir attribute of the task to specify the full path of the
devenv.com executable.
Here's
how I do it...
basedir="${VS.devenv.path}"
workingdir="${build.workdir}"
commandline='${
Dustin,
What version of NAnt are you using ? Can you post the build fragment that
fails ?
Gert
PS. What are the issues that you're running into with the task ?
- Original Message -
From: "Dustin Aleksiuk" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, January 04, 2005 3:07 PM
Subject: [Nant
Dustin,
In your , is the pathname with the space put in double quotes?
Merrill
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almo
Christopher,
I believe the default failonerror attribute of the task is true,
which is what you want. Could it somehow have been set to false, thereby
letting ignore the failure?
Merrill
---
The SF.Net email is sponsored by: Beat the post
16 matches
Mail list logo
