Hello Ivan, 

Thanks for the quick response. Unfortunately though I'd already tried your
suggestion without success - in fact I was convinced that was going to be
the answer as well. 

I've currently got the Draco service running under my own logon account
(which also belongs to the admins group). I've remapped the R: drive locally
using the subst command so everything is self-contained on the one machine,
but whatever I seem to try the Draco invocation just won't pick up the
referenced assembly. 

Phil    

-----Original Message-----
From: Ivan Tarasov
To: Phil Knight
Sent: 15/10/2003 14:53
Subject: Re: [nant-dev] Draco.NET invocation and locating assembly
references

Hello Phil,

I'm not sure if this is the real problem but it seems to me that it is
the case: if you run draco as a service, it is run under LocalSystem
account, thus it is not allowed to work with the network folders (even
mapped, as I recall). Try to do the same thing on your local system,
without mapping net folder, if it helps, then just create appropriate
account for draco service

PK> I apologise in advance that what follows probably isn't 100%
relevant to
PK> nant, but I'm really hopeful that someone here might be able to set
me in
PK> the right direction and end hours of frustration. 

PK> I've set up a basic build system using nant and Draco.NET which
appears to
PK> be working well for simple solutions/projects. I've just started to
test it
PK> out on more complicated projects and have hit a problem compiling
projects
PK> that reference external dlls. I'm using the solution task to do the
compile
PK> and the dlls in question reside on a shared network drive and are
referenced
PK> via a drive mapping (R:) configured on every developer workstation. 

PK> A simple nant build file to compile the project using the solution
task
PK> works fine when executed from the command line, the problem starts
when
PK> Draco launches the exact same build file, with nant reporting that
it can't
PK> find the referenced assembly. 

PK> I've included a copy of the simple build script that demonstrates
the
PK> problem plus the output from the command line invocation (correct)
and Draco
PK> invocation (incorrect).

PK> I'm at a bit of a loss as to where to begin with this one. Only
thing I can
PK> think of at present is there's some kind of permissions thing going
on (I've
PK> tried some of the more obvious things like giving the shared folder
full
PK> access to 'everyone' but without success). 

PK> I'd be eternally grateful to anyone who can give me any pointers. 

PK> Phil 


-- 
Best regards,
 Ivan                            mailto:[EMAIL PROTECTED]


------------------------------------------------------------------------------
DISCLAIMER: This email and files transmitted are confidential and are intended
solely for the use of the intended recipient.  If you are not the intended
recipient, or the person responsible for delivering it to the intended
recipient, you may not copy, disclose, distribute or use it in any
unauthorised manner.  If you have received this email in error please notify
us by telephoning on 01902-554455 or by email to
[EMAIL PROTECTED] and then delete it and any attachments
accompanying it.  Please note that Wolverhampton City Council cannot guarantee
that this message or any attachments are virus free or have not been
intercepted and amended.
Any views or opinions expressed within this email are those of the author and
may not necessarily reflect those of Wolverhampton City Council and no
contractual arrangement is intended to arise from this communication.
==============================================================================



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to