Hello nant-developers,
I want to discuss some ideas I have on failures which occur during the
build process. I've been desperately trying to solve the problems
which I'm going to address in this letter using the standard features
of NAnt and I've found that the ways by which I can solve these
So, the question is: should I start developing the trycatch task and
also leave the onFail part for targets?
Have anybody really analyzed the way in which I've done onfail -- do
you have some claims on its implementation?
Also, how should I address the problem of getting log only for the
part
Hello,
unfortunately, I've lost the track of the current development of nant
and now I just can't catch up (I haven't had the e-mail in september,
thus I've missed lots of things which were going on since the 0.8.3).
I'm using nant-0.8.3 and waiting for the next stable version to join
the
Hello Jason,
MJ My vote would be for one distribution package with the binaries for each
MJ .NET framework in separate directories. I don't think that we should
MJ include the documentation or source in the distribution package. We
MJ should instead, direct users to the website for
Hello Matthew,
when you add existing file to the project (in VS.NET), in the open
dialog the Open button has an arrow on the right side. By clicking
on this arrow you activate the popup menu in which you can choose
Link. In that case the file is not copied, in the project the xml
attribute Link
Hello Gert,
The similar thing happened, as I recall, in nunit2 task, it prints
0x0d after printing the tests results.
GD Nick,
GD This is now fixed in cvs.
GD Thanks for the report,
GD Gert
GD - Original Message -
GD From: Nick Varacalli [EMAIL PROTECTED]
GD To: [EMAIL PROTECTED]
GD
Hello,
I'm using nant-0.8.3 for our builds and yesterday I have found a
problem. I know that lots of things have changed in solution since
the release, still I hope this problem to fixed in the 0.8.4.
When building solution which uses embedded resource (doc.bmp in the
example below) and the file
Hello Martin,
MA locking problems occurs only to assemblies bigger than 64kB. Do you test it
MA with larger assemblies?
I do. From VS2003 I have to workaround such problems (by unloading
project which references the locked one), but I don't see why we have
to take it into account -- as far as I
Hello nant-developers,
I've found a bug in resource compiling (for dependent resources):
(according to nightly build from 28.11.03) in Resource.cs:104 there
is a regex which extracts namespace name and class name. The problem
is that it expects that the class is derived from something (it
Hello Matthew,
I've implemented the proof-of-concept program, which creates AppDomain
and loads assemblies there, but I'm not sure if it works around the
problem you've described. Probably it would be good to set up some
security policy for the newly-created AppDomain, so that the loaded
assembly
Hello Matthew,
I've fixed the current implementation of Reference.cs in VSNet-tasks
project. Now it creates new AppDomain in which it tries to resolve all
assemblies which are referenced from the given assembly, which are
located in the same directory. Recently, all assemblies in that
directory
Hello Matthew,
MM Looks pretty good to me. Do you notice an impact on compile speed?
I don't. I'm building from remote login session to two-processor
Pentium 4 :-)
But if all of the dll's are copied my build fails because it tries to
run tests on dll's in some subfolders which need config files
Hello Martin,
MA Yes, the echo would show: Prop: 2. Our primary use is to report
MA unit tests that fail at the end of a lengthy build process. We
MA have nearly 100 C# projects, plus several non-managed C++. Our
MA build system compiles the code for a particular project and then
MA compiles and
Hello Scott,
SH The reason, please correct me in my memory is off, for the deprecation of
SH the force attribute was because of the change to the call/ task to do
SH this by default. The idea was that if you want the behavior of dependencies,
SH you will use that mechanism (via the depends
Hello Martin,
It's a good idea, still it is a bit complicated to deal with xmlpeek,
if you need a single value. Surely, function will help a lot.
MA What I want to do is something James and Ivan also proposed: add some way to
MA return information from task back to script. I dont think that add
Hello SourceForge.net,
I have already sent a report here and also sent a patch which searched
through the dependency list recursively and only the referenced
assemblies from given directory were copied. For more info you may
take a look at my letter dated 4 Dec 2003 20:21:50 +0300, or I can
Hello SourceForge.net,
I have already sent a report here and also sent a patch which searched
through the dependency list recursively and only the referenced
assemblies from given directory were copied. For more info you may
take a look at my letter dated 4 Dec 2003 20:21:50 +0300, or I can
Hello Nicklas,
probably, the best way to fill the gap would be to implement
try/catch/finally task as it is done in Ant. I considered starting
to implement this functionality, but at the time I learnt about the
way it is done in Ant, I'd already made the onfail patch which we
use now in our
18 matches
Mail list logo
