I think I have discovered a bug or a feature I'd love to have implemented.
I'm using the solution task to Build my app.
Right before, I call the solution task, I call xml poke on all the .csproj
files to ensure
TreatWarningsAsErrors = "true".
Then I BUILD the app using the solution task. Ho
Hello, I'm trying to exec devenv.exe using the exec task. I know that there is a task, but it throws up errors that I don't get when building straight from devenv.exe. We've decided that we want to run from devenv.exe to make sure our CruiseControl build is totally consistent with our Visual Studi
NDoc works as expected when run from the
GUI, but when I use the NAnt task, I get an error. Since the NDoc.Documenter.HtmlHelp2.dll
is located in the same dir as NDocConsole.exe, I’m not sure what’s
failing:
locate-ndoc:
[echo] NDoc located at ..\sdktools\NDoc 1.2\bin\.net-1.
Hart, Leo wrote:
Oh, I didn't realize I could still use the comma-delimited list in the
syntax. I'll use that as a workaround
for now and request the desired functionality in an enhancement request.
And its definately somthing I'd like to see happen. I've just been
looking at how msbuild def
Hi again,
Because of a situation outlined in my prior post, “The
failure of success, or, but I really didn't want to do that...”, it occurred
to me that there might be a situation where something that is happening in the “onsuccess”
task which could be considered a build failure. What
Title: Message
Howdy all,
I was going along as happy as a pig in
slop when I realized I might be needing to do a rollback if the entire build
was not successful. If the entire build, including all NUnit tests, is
not successful then what do I do? Do I want the assemblies that did bui
Title: Message
Oh,
I didn't realize I could still use the comma-delimited list in the
syntax. I'll use that
as a workaround for now and request the desired functionality in an enhancement
request.
Thanks for your quick reply Gert!
Leo
-Original Message-From: Gert Driese
Title: Message
Leo,
This is something we'll need to look into after the 0.85
release.
Right now, the only
thing you can do is use one element and set its namespace
attribute to a comma delimited list of namespaces to import (which is not
optimal ofcourse).
Gert
From: [EMAIL
Title: RE: [Nant-users] Error creating virtual directory!
I don't think I was clear.
On each webserver in our web farm we have multiple websites, each corresponding to a different NAT address. The commonality is that each server uses the same name for each website within the farm, such as S
Title: Message
Hello,
I have a question
regarding the section of the task. I currently
have 1 common build file that contains common tasks used by all of my
sub-application build files and then additional build files, 1 per
sub-application.
In 0.84 in order
to specify your imports yo
Andy,
in fact, if you're using RC1 of nantcontrib 0.85, then
deletes the VS.NET generated directory configuration from
iis and recreates it as a virtualdir. VS.NET shouldn't notice the
difference.
on another note, if you want to build an old version of your
project, why don't you:
- check o
Bala requested an example of
a C++ project build. Here is an example I have been using. It works
with the 11-15-2004
0.85 build of NANT (it has worked since May 2004 builds of nant without change.)
This project has two
targets, a pre-compile step that converts WinRT macros to C code (
I know that VBDoc is not part of NAnt, but I believe that this issue is NAnt
related rather than VBDoc related (though I could be wrong)
I have a build script that extracts doc comments using the VBDoc tool. The
script runs fine on the old version of nant I was using (nightly build
0.85_2004_06_3
13 matches
Mail list logo
