Setting up Nunit in external tools in VS2005

Hi,

Apologies if this has been covered before, but I couldn't find it in the
mailing list archives or with Google.

I have set Nunit (2.4.7) up in the VS2005 (pro, sp1) external tools menu
using the full path to nunit.exe, "$(TargetPath)" and "$(TargetDir)", as
described in the docs. However, when I run it on my unit test project (a
class library DLL) I get an "Assembly not loaded" exception for
"nunit.framework". If I look at the project configuration in Nunit then
the project path seems to have the intermediate directory
("...\obj\Release\..." instead of "...\bin\Release\...").

The way I got around it was to load the csproj file from the command
line using "$(ProjectDir)$(ProjectFileName)" for the arguments.

My questions are these:

1) Has anyone else had the same experience with target path being wrong?
Is this a VS2005 bug or could I be doing something wrong to launch
Nunit?

2) Are there any drawbacks to using the csproj rather than the compiled
assembly? I assume I will need to include all my unit tests in this
project.

Thanks.
-- 
David McMinn, MaxWell Downhole Technology Ltd
Discovery Drive, Arnhall Business Park, Westhill, Aberdeen, AB32 6FG
Tel:    +44 (0)1224 748320              Fax: +44 (0)1224 748330
Direct: +44 (0)1224 748324

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone