I'd recommend against comparing only filenames. This will likely end up
causing trouble down the line. VS.NET is certainly a mess when it comes
to hint paths, but I've found that they are generally accurate. I don't
even think it uses them half of the time. :)
Can you describe your
We solved this problem by creating a tool to update the .user files for
each developer. It scans the directory tree and then creates a .user file
for each .proj file with the correct reference path for that workstation.
brant
...
From: Martin Aliger [EMAIL PROTECTED]
To: Matthew Mastracci
This is done now. You can include the same file fom multiple places and
only the first one will get included. A message will get logged that
there was an attempt to include a duplicate file.
Recursive includes still raise an exception and I think thats how it
should be.
Ian
Its probably a
Odd... We simply check in .csproj files and leave .csproj.user files on
each machine individually. We haven't had any issues with this.
Are you perhaps talking about 3rd party references? Or GAC references?
I believe that even MSFT recommends copying files to a directory
statically-relative
Hi,
The attached patch for Element.cs allows case-insensitive lookup of
enumeration values in the build file.
A number of tasks use an enum to specify a closed set of task
parameters. For instance, the foreach task uses the LoopItem enum to
specify the type of iteration that should be done.
Hi again,
I found two more thinks:
1/ csc @temp-path\commands.txt do not start propertly, when temp-path is
in x:\documents and settings becouse of spaces in path
2/ when extra output files are copied and source and dest is in same path -
source is deleted! (I change smthing in /doc stuff, but
Hi all!
I have a problem with Nant built from CVS an hour ago. My build file that
used to work with some older versions of Nant, fails when used with new
version.
The problem can be reduced to a simple *.build file
--
project
csc target=library output=aaa.dll
This used to be broken and was fixed. It sounds like a recent checkin
broke things again. The 1.27 revision of resgentask.cs broke things
(Mon Aug 18 11:58:18 2003 UTC (8 days, 6 hours ago) by drieseng).
GetOutputFile() depends on being able to tell if someone didn't pass in
todir. The change
I can't recall why I changed it ... I've reverted my changes for now.
Sorry for the hassle it caused.
Gert
- Original Message -
From: Erv Walter [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]; NAnt Developers
[EMAIL PROTECTED]; Gert Driesen
[EMAIL PROTECTED]
Sent: Tuesday,
Thanks Gert. Can you please make a new daily build and post it? I really
need to build my project asap and anonymous cvs is not very up-to-date so I
cannot rebuild from CVS.
Jarek
- Original Message -
From: Gert Driesen [EMAIL PROTECTED]
To: Erv Walter [EMAIL PROTECTED]; Jaroslaw
These should be fixed in cvs now.
Thanks !
Gert
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: ! nant [EMAIL PROTECTED]
Sent: Monday, August 25, 2003 10:46 AM
Subject: [nant-dev] Fw: two more problems in Solution task (path related)
Hi again,
I found two more
Jaroslaw, thank you. You just answered my question. ;) Great minds
and all that... When the student is ready, the master will appear.
Flipping the order of those two items solved my config file problem, and
all is right with the world again. Ergo, nevermind! As my eldest son
would say on
Still
learning as we go with this continuous integration project... To fix the
problem of PInvoke and its metadata (or whatever), I have to add the following
to nunit-console.exe.config:
startup
supportedRuntime
version=v1.1.4322 /
/startup
[Found
on
Hi all!
I have a question regarding NAnt.exe.config. Currently it has:
startup
supportedRuntime version=v1.0.3705 /
supportedRuntime version=v1.1.4322 /
/startup
I believe there are reasons for it to be reversed:
Imagine you have both .NET 1.0 and .NET 1.1 installed.
14 matches
Mail list logo
