Klaus Lüdenscheidt wrote:
i'm working with a solution which can't be compiled in Visual Studio (i
always get an error CS0013: could not write to ...pdb. Not enough memory).
To work around this problem i want to compile the solution via NAnt's
<solution> task. Outside Visual Studio it works fine. But when i integrate
NAnt in the Extras menu i somtimes get the error "could not copy file xxx.
It is used by another process" when the dll's of the referenced projects are
copied to a projects local bin directory.
It seems that Visual Studio locks the dll's. The solution contains 10
projects and there are references between the projects. I tried both project
references and dll reference with the same result.
Does anyone else tried to integrate NAnt in Visual Studio and found a
solution for that problem?
We solved it in-house by creating a new solution configuration based on
the Release configuration and called it "NAnt". The NAnt configuration
disables all the projects and uses Makefiles to call NAnt to build the
debug configuration.
Because VS.NET thinks you are building in release mode, it locks release
files and lets your debug build work perfectly. The only problem with
this solution is that VS.NET's default intellisense doesn't work
properly in this mode.
The solution for the intellisense problem is to shell out for a copy of
Resharper from Jetbrains. Their intellisense is source-code based,
rather than DLL-based like VS.NET. :)
Matt.
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
