Yes, thanks - that confirms what I had thought.
Richard
On Fri, Jun 1, 2012 at 3:29 PM, Ryan Boggs wrote:
> Hi,
>
> That's because the nunit2 is running on the framework that NAnt is
> currently running on. Which is the highest version of the .NET
> framework found on
with 0.92rc1. What can I do about it?
Is this because is run as a different process, whereas
is run in the same process as Nant?
Thanks,
Richard
-- Forwarded message --
From: Richard Birkby
Date: Mon, Oct 24, 2011 at 9:51 AM
Subject: CLR4/CLR2 NUnit binding
To: nant-us...@li
that correct?
Additionally, while I don't use the style task, I notice you aren't caching
the compiled XSL transform between runs. This means you will incur a
compile on every invocation. This will kill performance for users
transforming many files.
Richard
On Thu, Feb 23, 2012 at 4:31
The 450 LOC which implement this can be seen here:
http://nhibernate.svn.sourceforge.net/viewvc/nhibernate/trunk/nhibernate/src/NHibernate/Logging.cs?revision=5132&view=markup
It binds dynamically by using compiled linq expression trees.
Richard
On 19 May 2011, at 19:34, Ryan Boggs w
NHibernate solved that by building a logging proxy into NHibernate.dll
and then dynamically binding to log4net.
Are the licenses compatible? You could borrow their implementation.
Richard
On 18 May 2011, at 23:26, Ryan Boggs wrote:
> The problem isn't NAnt targeting net-4.0-clie
An MSBuild task isn't listed on:
http://nant.sourceforge.net/release/latest/help/tasks/
Is this new in 0.9a1?
Richard
On Sat, Apr 3, 2010 at 1:48 PM, Dominik Guder wrote:
>
>
> > The bug which I was unable to enter is that when I use Nant-Contrib's
> > MSBuild ta
Hi Ryan,
Looks great now. I've KDiff3'd the nant build output and can't see any
problem versus 0.86b1
Cheers,
Richard
On Sat, Apr 3, 2010 at 7:49 AM, Ryan Boggs wrote:
> Hey Richard,
>
> Would you mind giving the latest nightly file a try (04-02-2010)? We
> belie
e
with no carriage returns.
Thanks
Richard
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See
MSBuild, while it can only understand VS2005 format project files, can
target other frameworks. Check out the codeplex projects called MSBee, which
essentially a set of addons to MSBuild to target the 1.1 framework. I also
ended up wrapping msbuild in Nant in a task that provides some of the
functi
Ram, part of the difficulty you're having is that you're equating MSBuild to
the Nant Solution Task, when the correct analogy is to the Nant engine
itself. In that sense, of course there wouldn't be a property on the MSBuild
task for an output directory, just like there isn't a attribute on the on
On Wed, 2003-09-24 at 15:23, Gert Driesen wrote:
> Hi Richard,
>
> You might have to manually update the path to your mono installation in the
> following attributes of the mono-1.0-linux framework node in root>\src\NAnt.Console\NAnt.Console.exe.config.linux :
>
> sdk
* [all] Error 2
Any ideas what might be causing this build failure?
Best,
/Richard
--
"UNIX is basically a simple operating system,
but you have to be a genius to understand the simplicity."
---
This s
sting assemblies (dll's in the same folder) that contain components
that derive from Task. That way folks can extend NAnt without having to
worry about being kosher with the core.
Again I hope I didn't dilute the thread with "another voice". =)
- Richard
- Original Message ---
Has anyone started on the FTP task? If not I might be able to sling some code.
Richard Caetano
[EMAIL PROTECTED]
http://www.stronglytyped.com
14 matches
Mail list logo
