Francois ,
When I look in the manifest of the nunit.framework that we ship with
0.84 its referencing System.Xml with version:
.ver 1:0:3300:0
not
.ver 1.0.5000.0
as that trace indicates its looking for. So I'm pretty sure we are
shipping nunit.framework build for 1.0.
Could you please sen
Hi,
I am experiencing the same problem. From my discovery so far. Its
with NUnit being compiled against .NET v1.1 framework while your
current framework is v1.0. (I am assuming u have only .NET v1.0
framework like myself). Since, we can't have .config files for
assemblies I don't know what to d
Tony,
Check the image base value that is specified in the project settings (I cannot
remember where it is at exactly). I noticed while using the solution task before, that
Visual Studio will ignore some invalid values when it builds, but the solution task
uses them all.
I recommend resting any
Hi Scott
I tried with build of 2003-12-13 but with the same results.
Some further investigation revealed the following:
The main difference between the IL file (generated with ildasm) of the
working (VS built) EXE and the "broken" EXE appears to be the ".imagebase"
value.
Working EXE - .imagebas
I have the same problem, even if I set an output directory at the solution
level. Is there a way for the referenced projects to be copied to the output
directory? Or should I manually copy it?
> From: Harvey Green
> Subject: [Nant-users] Solution task not copying referenced dlls to output
dir
>
Carel,
You *do* need to use a child element. However if you just
add it like:
...
nant should take care of the rest for you. There were some issues with
resource handling in the last rc so you'll be better off trying a recent
nightly build [1]. Which version are you running by th
Hi
I'm currently struggling to get a WinForms app compiled with Nant running.
It works fine when compiled with the VS IDE. I get a
MissingManifestResourceException when executing the application. Here is
the nant scipt:
