ResolveReferences does not correctly walk all references in dependent projects - by Cory Foy1

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 383199 Comments
Status Closed Workarounds
Type Bug Repros 6
Opened 11/20/2008 12:54:31 PM
Access Restriction Public


We are using msbuild with the /t:ResolveReferences;_CopyWebApplication to simulate the publish of our websites. We've discovered that if the website references a project, which in turn references a DLL not via project references, that DLL will not be copied to the websites bin folder. 

I've been able to duplicate this (see below) by creating an set of test projects.
Sign in to post a comment.
Posted by Microsoft on 3/16/2009 at 5:09 PM
Glad to hear it worked.


Posted by Cory Foy1 on 3/12/2009 at 11:05 AM
Hi Chuck,

Perfect. Making the command line /p:Configuration=Release;OutDir=C:\inetpub\wwwroot\;BuildingProject=true worked like a charm. Thanks for your help!

- Cory
Posted by Microsoft on 3/12/2009 at 10:33 AM
Thanks for this bug!

If you add a parameter to your command line, "/p:BuildingProject=true", then you should get the correct results. This is really a work-around, as there is a bug in the targets file. You should be able to set the command line variable "/p:_ResolveReferenceDependencies=true" to do this.

Please try this and let me know how it works.

We are looking at fixing this in the current release.


Chuck England
Visual Studio Platform
Program Manager - Project and Build
Posted by Microsoft on 11/20/2008 at 7:15 PM
Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team