Is the solution correctly configured? In Visual Studio right-click on the
Solution and select Configuration Manager. Are the projects that are failing
to compile checked?
_
Jonathan Evans http://my.csintra.net/mypage/m253464
_
From: [EMAIL PROTECTED] [mailto:[EMAIL
This is a contentious point. Signing serves several purposes:
1) It implies a degree of security in that in a closed-source model
theoretically only the original vendor is able to sign their assemblies;
2) It is part of a type's identifier and so suggests an adherence to a
particular
I have a build with 35 projects that I am compiling with individual build files
using csc called from a master build file. Including a huge amount of ndoc
documentation it only takes about 20 minutes. How big are your projects and
how slow is your build machine?
_
Jonathan Evans
file paths, does it
make it quicker?
_
Jonathan Evans http://my.csintra.net/mypage/m253464
_
From: Rosy Malhotra [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 27, 2007 12:56 PM
To: Evans, Jonathan (2); Jay Flowers; [EMAIL PROTECTED]; nant-users
Subject: RE: [NAnt-users
Failing NAntContrib having service start/stop you could always call out to net
start and net stop.
Jonathan Evans
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Sayers
Sent: Friday, February 09, 2007 2:44 PM
Are you using .NET 2.0? If so, the problem could well be because NDoc doesn't
support .NET 2.0. There are some builds around that have been adapted, but the
project is now unmaintained and doesn't look as if it is getting any new
development.. Have a look at Sandcastle (from Microsoft) for
You might want to look at Ant and its CC task:
http://ant-contrib.sourceforge.net/cc.html
Jonathan Evans
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Archer
Sent: Monday, January 29, 2007 9:16 PM
To: Tolly
Sounds like you need the nantschema task - this will generate a schema for NAnt
as it is set up in your environment - that includes extra tasks and so on.
http://nant.sourceforge.net/release/latest/help/tasks/nantschema.html
Jonathan Evans
-Original
Use Version on its own
instead of '${Version}' and it should work - it is already enclosed in
braces, so it is already being treated as a variable.
Jonathan Evans
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Vrata
CermakSent: Tuesday, November 14, 2006 2:36 PMTo:
I used exactly that approach but as our projects grew larger ended up with
massive files and awkward configuration. As a result we have developed a
series of custom tasks that simplify the configuration and management a lot.
We had a set of include files (global, solution, project), a
There are definitely cases where having compiled a couple of base projects the
dependency tree then starts separating off into unrelated branches. And having
compiled one dll it is immediatly possible to start testing or documenting it
whilst the build process moves onto the next dll.
I think you need to look at the Copy task and FilterChains as a means of
modifying files as you copy them:
http://nant.sourceforge.net/release/latest/help/filters/replacestring.html
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Flex
Sent: Wednesday,
if test=${long::parse(x)} != 0
should be:
if test=${long::parse(x) != 0}
^
|
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Stephen
Tunney
Sent: Monday, January 09, 2006 5:19 PM
To:
, MCAD.NET
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Evans,
Jonathan (2)
Sent: January 9, 2006 12:25 PM
To: nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] Integer value comparisons
if test=${long::parse(x)} != 0
should be:
if test=${long
I have a VB6 project that does all of that - you may be able to adapt it to be
called from VB script. Would you like a copy?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Robert
Schneider
Sent: Wednesday, October 05, 2005 11:07 AM
To:
If you include an XMLNS reference in the project element of you build file, and
it points to the wrong place, then you build may well fail. I just spent an
hour tracking downa weird bug which finally turned out to be caused by the
xmlns entry. The problem I was having was caused by an
Make
has always been used in conjunction with shell scripts and other tools; it
functions largely as dependency-sensitive glue binding together all of the
commands to build and link C programs. So, if pressed, one could probably
write all of the things you mention using Make. The point of
I've been doing it using properties (which are inherited by child build
files). If there is a better way I'd be interested in knowing.
Jonathan Evans eml: [EMAIL PROTECTED]
CREDIT | First17 Columbus Courtyard tel: +44 (0) 20 7888 6145
SUISSE | Boston London
Title: Message
If
it is in a separate folder in VSS you can open properties and mark it as a
hidden folder (for the user that your script fetches as). The better
solution is to just delete it though.
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On
Title: csc Task Strategies
I have
tried fixing a vaguely similaryproblem. My solution was far from
perfect, but doesmake the maintenance task slightly easier. I have
created a separatebuild script for each assembly and then a master script
that refers back to the separate scripts. This
Hello,
I am working with a fairly complex project (20-30 assemblies) and would like
to be able to simplify the build files. I have experimented with using
properties in the targets, eg:
target name=build description=Compile source code.
21 matches
Mail list logo
