.

The issue is in the Descriptor implementation for the plugin. When it verifies the NAnt installation location, it looks for the existence of [NANT_HOME]/bin/NAnt.exe as this is the default location on Windows. I will have to update this to work in both a Windows and Unix-based environment.

However, some conventions must be established, and there is not going to be any way to satisfy 100% of NAnt installation scenarios. For instance, on Windows the plugin will continue to assume that the NAnt executable is located at "[NANT_HOME]/bin/NAnt.exe", as this is the default location if you download the NAnt binary package. I am not sure what the convention on Unix-based platforms will be yet, because I am not familiar with NAnt outside of Windows. Whatever the convention eventually is, I can tell you it will be based on the relative location of the NAnt binary that is installed when running "make install" from the NAnt sources pacakge. If a Debian/Ubuntu or RPM binary package installs the NAnt binary at a different relative path from the NANT_HOME directory, then symbolic links will need to be used.

Once the fix is in place, I will update the documentation on the plugin wiki page.

>The issue is in the Descriptor implementation for the plugin. When it verifies the NAnt installation location, it >looks for the existence of [NANT_HOME]/bin/NAnt.exe as this is the default location on Windows. I will have to >update this to work in both a Windows and Unix-based environment.

Thanks and I apologize so I didn't see [NANT_HOME]/bin/NAnt.exe in the Descriptor implementation. I'm so sorry.

>However, some conventions must be established, and there is not going to be any way to satisfy 100% of NAnt >installation scenarios. For instance, on Windows the plugin will continue to assume that the NAnt executable is >located at "[NANT_HOME]/bin/NAnt.exe", as this is the default location if you download the NAnt binary package. I >am not sure what the convention on Unix-based platforms will be yet, because I am not familiar with NAnt outside >of Windows. Whatever the convention eventually is, I can tell you it will be based on the relative location of >the NAnt binary that is installed when running "make install" from the NAnt sources pacakge. If a Debian/Ubuntu >or RPM binary package installs the NAnt binary at a different relative path from the NANT_HOME directory, then >symbolic links will need to be used.

I totally agree, anyway, there is a minor enhacement you could do to improve the windows/linux support. Windows is case insensitive, Linux is case sensitive so if you can code the plugin to search for nant.exe instead of NAnt.Exe, this fix will work under both operating systems (with the right path setup, of course (via plugin, via symlink...)).

Greats.

The fix will be tested against NAnt running in Linux (via mono). If the default location for the NAnt binary is /usr/bin/nant then I will make sure that if the platform is Unix-based the Descriptor will do a case-sensitive search for [NANT_HOME]/bin/nant. I should hopefully have a fix ready in the next few days, time premitting.

I am changing the priority of this issue to "Major". There is a workaround for this issue, creating a symbolic link, that is described in the original ticket summary. Therefore, this issue is not blocking the use of the plugin on Unix-based systems, just making it inconvenient.