Hallo,

We are using team foundation builds on a buildserver. That working fine.
We have several thirdparty assemblies located in folders on a network share.
And we have several own common team projects, which assemblies are used in
other team projects. We drop this common assemblies also in folders on the
network share.
In the build project file I use the AdditionalReferencePath itemgroup to
point to the correct folders on the network.
My problem is that all these referenced assemblies during the build are
copied to the binaries folder and thus also to the drop location. In my drop
location I want only to have the binaries of my project.
Is there a general option or so which I can add to my build project files to
prevent the copy local of the referenced assemblies?

Regards,

Jaap

Dear Jaap,

We need to perform more research on this issue . We will reply here as soon
as possible.
If you have any more concerns on it, please feel free to post here.

Thanks for your understanding!
Best regards,
Wen Yuan
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Dear Jaap,
Thanks for your waiting.

Under my research these days, I notified the SkipDropBuild property could
prevent coping of output assemblies to drop site.
http://blogs.msdn.com/manishagarwal/archive/2006/03/24/559693.aspx
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=464668&SiteID=1

However, I'm afraid there is no general option to prevent the copy local of
the referenced assemblies. I think this is because VSTS doesn't know which
assemble is referenced assemble and which assemble is not. It should copy
all assembles to drop sit. Thus the application could works fine at drop
site.

In my opinion, one way to achieve this is that creating add-in to catch the
build event and delete assemble from drop site. As you see, I'm afraid this
is not an easy way...

Hope this helps. Have a great day, thanks.
Sincerely,
Wen Yuan
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Dear Jaap,

Under my research these days, I got some reply from product team as below.
I think I need pass this information for you. Hope this helps.

Well, I don't see anything obvious that you can set globally. When you have
a reference that is marked as "Copy Local", Visual Studio marks the
reference as <Private>true</Private>. The only thing I can suggest is to
set Copy Local to false on each of the references. It doesn't sound like
that's what you wanted to hear, but it is the simplest answer. Another
option might be to override the copy binaries target to exclude them, but
that seems unstable.

Sincerely,
Wen Yuan.
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.