Kinook Software Forums

Go Back   Kinook Software Forums > Visual Build Professional > [VBP] Third Party Tools

Thread Tools Rate Thread Display Modes
Old 07-05-2007, 12:49 PM
JonathanMurray JonathanMurray is online now
Registered User
Join Date: 07-05-2007
Location: South Africa
Posts: 1
Question Make VS.NET action not obeying "Copy Local" setting of referenced assemblies

Hi all,

We are experiencing a problem with the “Make VS.NET” action of Visual Build where it does not copy some of the referenced assemblies for certain projects in our C# solution even though "Copy Local" is set to True for all those references.

When we build the solution with Visual Studio 2005 the output bin directory for the project correctly contains the projects’s own DLL and all referenced DLL's (as well as their own references).

But when we build the solution using Visual Build's "Make VS.NET" action, it builds successfully but only outputs the projects’s own DLL and some of the refrenced DLLs (and their sub-references), but some of the referenced DLLs are not copied to the output bin directory at all.
We also have a case where a referenced DLL is copied but some of it's sub-references are not.
We have another case where another project in the same solution is referenced with copy local but it's DLL does not get copied to the refering project's own output bin.

I cannot find any setting in the Visual Build action definition that would change this behaviour from what is expected. It is also puzzling why some of the Copy Locals are done. On what basis might it making the exclusions?

It all works fine when built in Visual Studio 2005.
Can anyone perhaps shed any more light on this for us?

Thank you,

Jonathan Murray
Reply With Quote
Old 07-05-2007, 01:05 PM
kinook kinook is online now
Join Date: 03-06-2001
Location: Colorado
Posts: 5,757
It sounds like an issue with Visual Studio when building from the command line (what the Make VS.NET action ultimately invokes to actually build a solution or project). You can verify this by checking the 'Display command-line...' checkbox on the Options tab, rebuilding the step, then copying and pasting the msbuild/devenv command-line from the build output to a Command Prompt and running it from there. If it occurs outside of VBP, you'll need to open a support incident with MS. Otherwise, we'll need a reproducible case to investigate further, including:
1) The info from Help | About | Install Info
2) The .bld file used to build
3) A build log file
4) A .sln file and project files (no source code files)

Also, building with devenv (select 'devenv' in the Override field on the Options tab) rather than msbuild will tend to perform a build that more closely resembles what the VS2005 IDE does when building and may help.
Reply With Quote

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

All times are GMT -5. The time now is 06:45 PM.

Copyright © 1999-2019 Kinook Software, Inc.