Hello, you are right - this is problem in current setup. I was also point to that, but there are some problems how to find references to assembly without lock them. Current framework sometimes locks assemblies when you load them (even into another appdomain). VS2003 has also problem with it [cannot copy because another process use this file error]
If you have some another method how to find those references, send it here! [possible also as path to reference.cs] Regards, Martin ----- Original Message ----- From: "Ivan Tarasov" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 02, 2003 11:25 AM Subject: [nant-dev] project references problems in <solution> task > Hello nant-developers, > > I have quite a big project which uses <solution> task to build > certain .csproj projects. There is a build directory, some projects > are built into specific subdirectories of this build directory. > > Consider following dir structure: > > build > | > +-ProjectA > > During the build I have some projects built directly into build > directory. ProjectA is built into the respective folder, but it > references some dll's in build directory and has CopyLocal set to > "true" for these references. Thus, as we can expect, these dll's > are copied to ProjectA directory. The problem is that not only these > dll's (and the dll's which they reference) are copied to ProjectA, > but all dll's in build directory! > Thus, I have lots of dll's in ProjectA which shouldn't be there. > > VS2003 is smart enough to copy only those libraries, which are > referenced from the project. I've tracked down where the solution > task does it wrong (in the latest nightly build it is > Nant\src\NAnt.VSNet\Reference.cs:265-278. > > I've written little program which finds all the referenced assemblies > in the current folder (for the given assembly) (it was just a > proof-of-concept). I'm going to add this code to Reference.cs (it > will add just two methods and a call to one of them instead of > "Directory.GetFiles(fi.DirectoryName, "*.dll")" in line 265, but I > need to clean the code up a little bit. > > If anybody can comment upon that change, please let me know. > I will send the patch here after the clean-up. > > -- > Best regards, > Ivan mailto:[EMAIL PROTECTED] > > * To err is human. To really foul up you need a computer. > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
