VS 2010 Publish Web Deployment not copying child dependency project assemblies - by Wolfenator

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 690515 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/23/2011 12:00:53 PM
Access Restriction Public
Moderator Decision Sent to Engineering Team for consideration

Description

When deploying an asp.net mvc web site an assembly is not being copied to the output directory of the publish process.

I've tested this w/ asp.net web forms and asp.net mvc 3 sites.

Steps to recreate:
Create a new web site. (Web Site)
Create a new class library. (Project A)
Create a second class library. (Project B)
Reference Project A into the Web Site.
Reference Project B into Project A.
Right click on Web Site project and select Publish.
Select "Publish method" as File System.
Select a "target location".
Click Publish button.
Upon completion, open destination folder and observe Project B.dll is missing.

Work around:
Reference Project B into Web Site.
This is not ideal as it gives direct access to the Project B functionality, database access in our case, to the web site.  If someone goes rouge, they can potentially write database manipulation in the web site's click event.
Sign in to post a comment.
Posted by Microsoft on 1/25/2012 at 5:32 PM
Hi Wolfenator,

The behavior you're seeing is currently by-design. The compiler only copies indirect references for which it can find a compile-time dependency. In this case, it determines that your Web project doesn't have a compile time dependency on Project B. Direct dependencies will always be copied. (See http://connect.microsoft.com/VisualStudio/feedback/details/108406 for another example of this issue.)

Thanks,
- Jimmy Lewis
SDET, Visual Web Developer team
Posted by MS-Moderator07 [Feedback Moderator] on 9/26/2011 at 12:56 AM
Thanks for your feedback.

We are rerouting 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.

Posted by MS-Moderator01 on 9/23/2011 at 12:46 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)