Bugs item #875674, was opened at 2004-01-12 21:05
Message generated for change (Comment added) made by qswinson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=875674&group_id=31650

Category: Tasks
Group: 0.85
Status: Open
Resolution: Works For Me
Priority: 5
Submitted By: qswinson (qswinson)
Assigned to: Nobody/Anonymous (nobody)
Summary: Solution task copies more than just referenced libraries

Initial Comment:
The solution task copies all libraries and related
files located in the referenced directory, not just the
library that is referenced. This is very time consuming
when all build assemblies are stored in a single
directory and referenced from that directory in the
project files.

For example, if the directory c:\test\bin contains
test1.dll, test2.dll, test2.pdb, and test3.dll and
project c:\test\test4\test4.csproj only has one reference:

<Reference
    Name = "test1"
    AssemblyName = "test1"
    HintPath = "..\bin\test1.dll"
/>

When this project is built with a solution task,
test2.dll, test2.pdb and test3.dll will also be copied
into the build directory even though they are not
referenced.



----------------------------------------------------------------------

>Comment By: qswinson (qswinson)
Date: 2004-02-25 18:25

Message:
Logged In: YES 
user_id=789833

I just tested with nant-0.85-20040224.zip. This issue did
not occur. Thanks all!

----------------------------------------------------------------------

Comment By: Gert Driesen (drieseng)
Date: 2004-02-25 17:31

Message:
Logged In: YES 
user_id=707851

I'm not able to reproduce the issue you're describing.  There 
have been some changes in the <solution> task recently, so 
this issue could be fixed.

Can you try this using the latest nightly build 
(http://nant.sourceforge.net/nightly/builds) ?

Note: there's a known issue (which we're looking into) with 
regards to namespaces in the buildfile, so you'll need to 
remove the default namespace from your build file.

Thanks !

----------------------------------------------------------------------

Comment By: qswinson (qswinson)
Date: 2004-02-25 15:50

Message:
Logged In: YES 
user_id=789833

I realized this morning that the build order in the sample
solution was wrong. Project NotReferenced needs to be build
before project Third in order for my argument to have any
merit. I added a project dependency in the solution from
Third to NotReferenced to ensure NotReferenced would be
built before Third in the solution.

----------------------------------------------------------------------

Comment By: qswinson (qswinson)
Date: 2004-02-25 00:05

Message:
Logged In: YES 
user_id=789833

I still feel that the true behavior of VS.Net is not being
duplicated in this situation. I've attached a sample
solution and nant build file to demonstrate this. 

Extract it directly to c: or change the post-build events. 

First build the solution with VS.Net. Look in
ExtraneousAssemblyCopies\Third\bin\Debug - there is no
assembly named NotReferenced.dll in the directory because
that assembly is not referenced by Third.dll, Second.dll, or
First.dll.

Now build using the nant file.
ExtraneousAssemblyCopies\Third\bin\Debug\NotReferenced.dll
now exists even though there is no assembly that references it.

Reminder - VS.Net will not clean directories before building
or rebuilding.



----------------------------------------------------------------------

Comment By: Gert Driesen (drieseng)
Date: 2004-02-22 10:10

Message:
Logged In: YES 
user_id=707851

I'll close this report, unless you have something to add to it or 
can provide us a repro ...

----------------------------------------------------------------------

Comment By: Nicklas Norling (exinor)
Date: 2004-01-22 19:21

Message:
Logged In: YES 
user_id=949257

Ok great then I agree with you :)

----------------------------------------------------------------------

Comment By: qswinson (qswinson)
Date: 2004-01-22 19:19

Message:
Logged In: YES 
user_id=789833

I agree that it is important to mimic VS for this task. VS
2003 copies the referenced assembly and indirectly
referenced assemblies to the build directory. It does not
copy the entire contents of the directory of the referenced
assembly. 

----------------------------------------------------------------------

Comment By: Nicklas Norling (exinor)
Date: 2004-01-22 17:33

Message:
Logged In: YES 
user_id=949257

The solution task is supposedly a Nant version of VS running build on a VS solution 
file. It would be a bad thing if this task would do things different from VS in my 
oppinion. I believe that the "extra" dll's are dependant dll's dependents. If you want 
to e.g. run unti tests in the bin/debug folder you need not only the output file it 
self, but everything it is in anyway dependant on. Even the most remotly dependant dll 
as far as I understand. So unless I've missunderstod .NET dependecies and dll's this 
should most definately stay as it is or loads of things might be broken.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=875674&group_id=31650


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to