nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

I changed the logic to try the following 3 strategies in order

1. If a well-known script or exe is on the path, use it

2. Try to find mono

3. Use "mono"

For step 1, the names sought are mono.bat, mono.cmd and mono.exe on
Windows, otherwise mono and mono.exe

For step 2, Windows examines the registry, nothing implemented on other
platforms

** Changed in: nunitv2
       Status: Triaged => Fix Committed

** Changed in: nunitv2
    Milestone: None => 2.5.6

-- 
NUnitConfiguration.MonoExePath returns wrong path
https://bugs.launchpad.net/bugs/602798
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.

Status in NUnit V2 Test Framework: Fix Committed

Bug description:
NUnitConfiguration.MonoExePath returns 'nunit-console.exe' when run on Mono on Linux. It should return the path to the Mono executable instead, e.g. '/usr/local/bin/mono'.

This happens in NUnit 2.5.5