It is. But you do not run builded assemblies during builds. Only the test
code is run (and through it the real code)
Martin
- Original Message -
From: Philip Nelson [EMAIL PROTECTED]
To: Martin Aliger [EMAIL PROTECTED]; !nant
[EMAIL PROTECTED]
Sent: Wednesday, September 10, 2003 5:25 PM
Title: [nant-dev] NUnit security
Hi Martin,
If you have no special need for your service to run under a privileged
account, let it then run with aless privilegedaccount.
Otherwise you can use the built-in .Net runtime security
features:
Let your nant script copy everithing you need to a
Title: [nant-dev] NUnit security
Seems ok.
It is not problem for me - just a general
thought.
Maybe we could add noteabout it into
doc for NUnit{1,2} tasks. Could be problem for projects like Draco.NET or
CruiseControl.NET which use Nant internally. The rights should be adjustablefrom task
Especially those people using Draco.NET to build Sourceforge projects. :)
Martin Aliger wrote:
Seems ok.
It is not problem for me - just a general thought.
Maybe we could add note about it into doc for NUnit{1,2} tasks. Could
be problem for projects like Draco.NET or CruiseControl.NET
Took a while to track this
one down.
I was trying to replace ${nant.Version}
when I should have been using ${nant.version}
Sigh
SQL Task Aborts when expandprops=true
and a ${property} has not been defined
The following Build Script
project name=SQL bug basedir=.
default=Bug
NAnt version 0.8.3 Copyright (C) 2001-2003 Gerry Shaw
http://nant.sourceforge.net
Buildfile: file:///D:/Build/Source/ClaimStation RichClient IR
1/Solutions/ClaimStation_RC_Solution_IR1/ClaimStation.build
build:
[solution] Starting solution build.
[solution] Included projects:
[solution]
Is there any work being done here? I noticed a few todos regaring
dependencies, etc. Since Im in need of this task, I might find some time
to work on this
however, have any thoughts been given to where/how to
store dependency info?
Tharen
Ian MacLean wrote:
I'm still fleshing out the details but basically infer the locale based
on the resx file name ( or allow it to be specified ) and then use
... or infer it if not specified?
assemblylinker to build the satellite assemblies.
So you plan a comfort feature of implicitly
